Rapid Indexer MCP server
online · 96% uptimecom.rapid-indexer/mcp·v0.1.0Send new pages and backlinks to Googlebot fast, then check which URLs Google has indexed.
0 stars
Reviews
Write oneNobody has reviewed Rapid Indexer yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Rapid Indexer tools (12, 4 write)
write = sends, deletes, buys or postscheck_index_statuswrite actionFreeCreate an index-check task that reports, per URL, whether Google currently has it in the index (indexed / unindexed). Cheap (~0.1 credit per URL) but still SPENDS CREDITS. Results arrive within a few minutes: poll get_task, then read get_task_links. Does not submit anything to Google; use submit_urls_for_indexing for that.
check_service_healthFreePing the Rapid Indexer API and report version and enabled features (indexer, checker, traffic, ctr). Also validates that the configured API key works.
create_ctr_campaignwrite actionFreeSend visitors who search the given keywords on a search engine (Google by default), find the target URL in the results and click it, then browse like a human. SPENDS CREDITS immediately (same rate as traffic, per visitor). Confirm with the user before creating. Use list_search_engines for valid search_engine values.
create_traffic_campaignwrite actionFreeSend AI-driven, human-like visitors to a URL (geo, device, referrer and on-page behaviour are configurable). SPENDS CREDITS immediately: see get_pricing (credits per 1,000 visitors). visitors/days must not exceed 1,000 per day. Confirm with the user before creating. Returns the task id; poll get_task for status.
estimate_costFreeEstimate the credit and USD cost of an indexing or index-check task before submitting it, and whether the account balance covers it. Does not create anything.
get_accountFreeReturn the authenticated Rapid Indexer account (id, email, credits balance, created date). Use it to check credits before creating tasks.
get_pricingFreeReturn live credit costs: credits per URL for standard/VIP indexing and index checking, traffic price per 1,000 visitors, USD per credit, and whether VIP/traffic are currently enabled.
get_taskFreeFetch one task, refreshing its status from the provider first. Returns status (pending/processing/completed/failed) and progress counts. Poll this after creating a task.
get_task_linksFreeReturn each URL in an indexing or index-check task with its status (indexed / unindexed / pending / error). Filter by status and paginate with limit/offset for big tasks. Always includes a summary count.
list_search_enginesFreeReturn the search engines and marketplaces accepted by create_ctr_campaign.search_engine.
list_tasksFreeList the account's tasks, newest first, with per-link counts (indexed / unindexed / pending / error). Filter by type or status. Use it to find task ids.
submit_urls_for_indexingwrite actionFreeCreate an indexing task: Rapid Indexer signals Googlebot to crawl each URL so Google discovers it fast. SPENDS CREDITS immediately (standard ~2 credits/URL, VIP ~10 credits/URL). Run estimate_cost first and confirm with the user for large batches. Standard queue starts within minutes; VIP starts immediately with priority. drip_feed spreads submissions over several days for a natural pattern. Returns the task id; poll get_task for progress and get_task_links for per-URL status. Google makes the final indexing decision.
Public scan report
scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1806ms20/20
- Tool poisoning12 tool descriptions checked15/15
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 6 days ago15/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
How Rapid Indexer compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 12
- the typical server has 7
- Tools that change things
- 33%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 96%
- of our recent checks; the typical remote server answers 100%
- Response time
- 385 ms
- faster than 38% of 30,031 servers
What its tools let an agent do: 8 read · 2 create · 2 change
Install Rapid Indexer in Claude Code, Cursor or VS Code
claude mcp add --transport http mcp https://mcp.rapid-indexer.com/mcp
What the publisher says
From the Rapid Indexer repository's README, as published. We do not edit it. Read it on GitHub
rapid-indexer-mcp
Model Context Protocol server for Rapid Indexer. It lets Claude, Cursor, ChatGPT, Claude Code and any other MCP host submit URLs to Googlebot, check whether pages are indexed, read task results and launch traffic / CTR campaigns using your Rapid Indexer API key.
Built on the official TypeScript SDK v2 (@modelcontextprotocol/server). Serves over stdio (local, one account) or Streamable HTTP (hosted, multi-tenant: each request carries its own API key).
Requirements
- Node.js 20+
- A Rapid Indexer API key: log in, open your account menu → API Access (https://rapid-indexer.com/api_access).
Quick start (stdio)
Cursor
~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"rapid-indexer": {
"command": "npx",
"args": ["-y", "rapid-indexer-mcp"],
"env": { "RAPID_INDEXER_API_KEY": "YOUR_API_KEY" }
}
}
}Claude Desktop
~/.config/Claude/claudedesktopconfig.json on Linux:
{
"mcpServers": {
"rapid-indexer": {
"command": "npx",
"args": ["-y", "rapid-indexer-mcp"],
"env": { "RAPID_INDEXER_API_KEY": "YOUR_API_KEY" }
}
}
}Claude Code
claude mcp add rapid-indexer -e RAPID_INDEXER_API_KEY=YOUR_API_KEY -- npx -y rapid-indexer-mcpFrom a local checkout (before publishing to npm)
cd mcp
npm install
npm run buildThen point the host at the built CLI:
{
"mcpServers": {
"rapid-indexer": {
"command": "node",
"args": ["/absolute/path/to/Rapid-Indexer-main/mcp/dist/cli.js"],
"env": { "RAPID_INDEXER_API_KEY": "YOUR_API_KEY" }
}
}
}Hosted mode (Streamable HTTP)
One process serves every customer; the API key travels with each request.
RAPID_INDEXER_BASE_URL=https://rapid-indexer.com \
node dist/cli.js --http --host 0.0.0.0 --port 3333 --path /mcpClients connect to https://your-host/mcp and send Authorization: Bearer (also accepted: X-API-Key: , or ?api_key= on the URL). GET /healthz returns a liveness JSON.
Cursor example for a remote server:
{
"mcpServers": {
"rapid-indexer": {
"url": "https://mcp.rapid-indexer.com/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}Put it behind TLS (nginx/Caddy) and run it with systemd or pm2. The server is stateless, so you can run several replicas. --api-key / RAPIDINDEXERAPI_KEY in HTTP mode is only a fallback for requests that carry no key (single-tenant self-hosting).
Tools
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Rapid Indexer: common questions
- Is Rapid Indexer MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Rapid Indexer safety report
- How do I install Rapid Indexer?
- It runs remotely at mcp.rapid-indexer.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Rapid Indexer need an API key?
- Yes. The registry entry asks for
Authorization. - Is Rapid Indexer maintained?
- The last commit was 27 days ago (2026-10-08). The latest release is v0.1.0.
- Is Rapid Indexer up?
- 96% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Rapid Indexer compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 12 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.