Hosted MCP server/Search

Rapid Indexer MCP server

Hosted at mcp.rapid-indexer.com·Streamable HTTP

Rapid Indexer sends Googlebot to URLs and verifies which URLs are in the index, and manages traffic campaigns from Claude, Cursor and ChatGPT. The live endpoint exposes 12 tools including get_account, get_pricing, estimate_cost, submit_urls_for_indexing, check_index_status, list_tasks and create_traffic_campaign. Authentication is an API key, sent as X-API-Key for the REST API or Authorization: Bearer for self-hosted HTTP. The provider's API docs describe the npx stdio server and self-hosted HTTP; the hosted mcp.rapid-indexer.com endpoint answered an initialize request on 2026-11-16.

mcp.rapid-indexer.com Streamable HTTP API key (X-API-Key for REST, Bearer for self-hosted HTTP) Source checked Nov 12, 2026 Server responded when checked Reviewed 2026-11-16
About

Where it fits

Search and marketing teams who submit URLs to Googlebot and manage traffic campaigns from AI clients.

  • Start with get_account to check credits.
  • Estimate cost, then submit URLs for indexing.
  • Check index status later with check_index_status.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local stdio server

Set the provider API key in the environment.

npx -y rapid-indexer-mcp

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://mcp.rapid-indexer.com/mcp
Host
mcp.rapid-indexer.com · /mcp
Transport
Streamable HTTP
Authentication
API key (X-API-Key for REST, Bearer for self-hosted HTTP)
Server name
rapid-indexer
Listing type
Community or directory listing

The installer uses the server name rapid-indexer. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that rapid-indexer appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Start with get_account to check credits. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server responded when checked

We reached mcp.rapid-indexer.com when we checked. That only means the address answered; it does not prove the MCP connection, sign-in, or tools work. The provider page blocked our automated check. Open it in a browser to confirm the setup.

Provider page blocked our check on Nov 12, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Rapid Indexer documentationhttps://rapid-indexer.com/api-docsGitHub repositoryhttps://github.com/rollounden/rapid-indexer-mcp