MCP Beta access
Try SEO MCP and Web Scraping MCP with a free beta allowance.
Need more credits? Contact our team to keep testing.
Begin with a small task and follow the returned usage and retry information.
When you reach your current allowance, message us through Tidio to request additional free beta credits.
Chat with us via Tidio, or use our contact page.
Additional beta credits are handled by our team. Your current allowance and service limits still apply. How report allowance is counted ↗
Size the requested work
Admission units measure the work requested. They are separate from monetary prices and provider credits. A valid request can still exceed the available allowance.
| Report | Admission units | Example |
|---|---|---|
| Rank tracking | Keywords × locations × engines | 3 keywords × 2 locations × 1 engine = 6 units |
| On-page SEO | Requested devices | Mobile and desktop = 2 units |
| Broken internal links | ceil(maxPages / 100) | 20 or 100 requested pages = 1 unit; 1,000 = 10 units |
| Backlinks | 1 per report | One selected backlink report = 1 unit |
| Keyword volumes | Keyword count | 10 requested keywords = 10 units |
Report admission units depend on the requested work: keywords × locations × engines for rank checks, selected devices for on-page reports, ceil(maxPages / 100) for broken-link checks (one unit for up to 100 requested pages), one unit for a backlink report, and keyword count for volumes. These are admission weights, not provider credit prices. A schema-valid request can exceed the configured allowance. A create call can count even when it reuses completed data; retrieval has separate limits. Setup and tool discovery do not submit reports. Respect returned limits and retry instructions.
Future scheduled rank checks can consume provider credits outside MCP per-request metering. A first-request allowance is not a cap on future spending. Enable a recurring schedule only when you intend it.
The client enrolls automatically and stores an installation credential and signing identity locally. You do not enter a reusable provider API key or create a GeoRanker account for the Beta trial. The two clients share installation state for the same service origin. This enrollment is not OAuth. The setup check verifies enrollment and tool contracts without submitting a data query; subsequent tool calls use the configured allowance.
Reviewed first-party documentation ↗Independent tasks may run in parallel within shared and per-installation service limits. For pending SERPs, retain jobId and call get_serp_result; for pending web pages, call get_fetch_result with the same jobId. SEO report families use their own reportId and matching get tool. Retrieval does not create a new data job. Follow returned nextAction and retry information, preserve pending, unknown and failed states, and avoid duplicate creation. Cancelling or timing out a call does not prove that submitted work stopped.
Reviewed first-party documentation ↗Report admission units depend on the requested work: keywords × locations × engines for rank checks, selected devices for on-page reports, ceil(maxPages / 100) for broken-link checks (one unit for up to 100 requested pages), one unit for a backlink report, and keyword count for volumes. These are admission weights, not provider credit prices. A schema-valid request can exceed the configured allowance. A create call can count even when it reuses completed data; retrieval has separate limits. Setup and tool discovery do not submit reports. Respect returned limits and retry instructions. For example, three keywords in two locations on one engine require six rank-report admission units. A broken-link request for 20 or 100 pages requires one unit; 1,000 requested pages require ten. None of these values establishes a monetary price or a fixed free quota.
Reviewed first-party documentation ↗GeoRanker MCP is in Beta. Request more free Beta credits through the website chat powered by Tidio, or use the contact page. Tell the team which MCP you use, what you are building and the workload you need. Our team reviews your request and confirms the allowance. The hosted service controls shared and per-installation allowances and concurrency, so follow returned limit and retry information. API calculator estimates do not define MCP Beta allowances or report admission units.
MCP Beta credit policy ↗