# Rapid Indexer (remote · mcp.rapid-indexer.com)

Send new pages and backlinks to Googlebot fast, then check which URLs Google has indexed.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.rapid-indexer.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-rapid-indexer-mcp/mcp.md), [page](https://verifymcp.io/servers/com-rapid-indexer-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.rapid-indexer.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2217 tokens (~184/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 89% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Rapid Indexer MCP server?

Rapid Indexer is a hosted endpoint at https://mcp.rapid-indexer.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-rapid-indexer-mcp 'https://mcp.rapid-indexer.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-rapid-indexer-mcp": {
      "url": "https://mcp.rapid-indexer.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-rapid-indexer-mcp": {
      "type": "http",
      "url": "https://mcp.rapid-indexer.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-rapid-indexer-mcp]
url = "https://mcp.rapid-indexer.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-rapid-indexer-mcp": {
      "type": "remote",
      "url": "https://mcp.rapid-indexer.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-rapid-indexer-mcp --url 'https://mcp.rapid-indexer.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-rapid-indexer-mcp:
    url: "https://mcp.rapid-indexer.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-rapid-indexer-mcp": {
      "Transport": "http",
      "Url": "https://mcp.rapid-indexer.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-rapid-indexer-mcp -t streamable-http -u 'https://mcp.rapid-indexer.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-rapid-indexer-mcp": {
      "type": "http",
      "url": "https://mcp.rapid-indexer.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 76, +2)

- [security improvement] Judged manipulation: unverified → pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_index_status” rewrote its description, which is the text the model reads
- [security] Tool “get_task_links” rewrote its description, which is the text the model reads
- [security] Tool “submit_urls_for_indexing” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 150 → 184
- [functional] Schema quality: excellent → good
- [functional] Server version: 0.1.0 → 0.2.0
- [cosmetic] “check_index_status” added an optional parameter “also_brave”
- [cosmetic] “estimate_cost” added an optional parameter “bing”
- [cosmetic] “estimate_cost” added an optional parameter “brave”
- [cosmetic] “estimate_cost” added an optional parameter “brave_check”
- [cosmetic] “submit_urls_for_indexing” added an optional parameter “also_bing”
- [cosmetic] “submit_urls_for_indexing” added an optional parameter “brave”
- [cosmetic] “submit_urls_for_indexing” added an optional parameter “brave_keywords”
- [cosmetic] “submit_urls_for_indexing” reworded the description of “drip_feed”
- [cosmetic] “submit_urls_for_indexing” reworded the description of “engine”
- [cosmetic] Tool “check_index_status” changed its title: Check whether URLs are indexed by Google → Check whether URLs are indexed by Google (and Brave)
- [cosmetic] Tool “submit_urls_for_indexing” changed its title: Submit URLs for Google indexing → Submit URLs for Google, Bing and/or Brave indexing

### 2026-10-26 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (12)

### `get_account` (~35 tokens)

Get account & credit balance

Return the authenticated Rapid Indexer account (id, email, credits balance, created date). Use it to check credits before creating tasks.

Output parameters:

- `created_at` (string)
- `credits_balance` (number)
- `credits_balance_usd` (number)
- `email` (string)
- `id` (number)

### `get_pricing` (~48 tokens)

Get current pricing

Return 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.

Output parameters:

- `bing_indexing_enabled` (boolean)
- `brave_indexing_enabled` (boolean)
- `credits_per_url` (object)
- `currency` (string)
- `price_per_credit_usd` (number)
- `traffic` (object)
- `usd_per_url` (object)
- `vip_queue_enabled` (boolean)

### `estimate_cost` (~179 tokens)

Estimate task cost

Estimate 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.

Input parameters:

- `bing` (string): Bing Indexing (indexer only): none, also (Google + Bing) or only (Bing, no Google).
- `brave` (boolean): Brave Search Boost (indexer only): free next to Google, priced per URL without Google.
- `brave_check` (boolean): Checker only: also look every URL up in Brave Search (extra credits per URL).
- `type` (string): "indexer" submits URLs to Googlebot; "checker" only checks whether they are indexed.
- `url_count` (integer, required): Number of URLs in the planned task.
- `vip` (boolean): VIP priority queue (indexer only): starts immediately, costs more.

Output parameters:

- `credits_balance` (number)
- `credits_per_url` (number)
- `shortfall_credits` (number)
- `sufficient_balance` (boolean)
- `total_credits` (number)
- `total_usd` (number)
- `type` (string)
- `url_count` (number)
- `vip` (boolean)

### `submit_urls_for_indexing` (~412 tokens)

Submit URLs for Google, Bing and/or Brave indexing

Create an indexing task: Rapid Indexer signals Googlebot to crawl each URL so Google discovers it fast. also_bing sends Bingbot to each URL too; engine "bing" sends Bingbot only. Bing is priced per URL (see get_pricing), in beta (not guaranteed) and only available while Bing Indexing is enabled. brave adds Brave Search Boost (signals to Brave's Web Discovery Project, free next to Google); engine "brave" sends Brave only. Not guaranteed. SPENDS CREDITS immediately (standard ~1 credit/URL, VIP ~5 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.

Input parameters:

- `also_bing` (boolean): On a Google task, also send every URL to Bing (Bing Indexing add-on, extra credits per URL).
- `brave` (boolean): Also add Brave Search Boost (free next to Google).
- `brave_keywords` (array): Optional search keywords for Brave Search Boost, used for every URL (turns Brave on).
- `drip_duration_days` (integer): Days to spread a drip-feed task over (only when drip_feed is true).
- `drip_feed` (boolean): Spread the URLs over drip_duration_days instead of submitting all at once. Standard queue only: not available with vip.
- `engine` (string): google (default), bing (Bing Indexing only, no Google) or brave (Brave Search Boost only, no Google).
- `title` (string): Optional label shown in the dashboard.
- `urls` (array, required): Absolute URLs (https://...). Scheme is added when missing. Max 10000 per task.
- `vip` (boolean): Use the VIP priority queue (faster, higher cost).

Output parameters:

- `dashboard_url` (string)
- `is_drip_feed` (boolean)
- `message` (string)
- `targets` (array)
- `task_id` (number)
- `url_count` (number)
- `vip` (boolean)

### `check_index_status` (~183 tokens)

Check whether URLs are indexed by Google (and Brave)

Create an index-check task that reports, per URL, whether Google currently has it in the index (indexed / unindexed). also_brave looks every URL up in Brave Search too (extra credits per URL, see get_pricing); its result is brave_status in get_task_links. URLs Brave cannot look up are refunded. 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.

Input parameters:

- `also_brave` (boolean): Also check each URL in Brave Search (extra credits per URL).
- `title` (string): Optional label shown in the dashboard.
- `urls` (array, required): Absolute URLs (https://...). Scheme is added when missing. Max 10000 per task.

Output parameters:

- `brave_check` (boolean)
- `dashboard_url` (string)
- `message` (string)
- `task_id` (number)
- `url_count` (number)

### `list_tasks` (~83 tokens)

List tasks

List 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.

Input parameters:

- `page` (integer)
- `per_page` (integer)
- `status` (string): Only tasks in this status.
- `type` (string): Only tasks of this type.

Output parameters:

- `pagination` (object)
- `tasks` (array)

### `get_task` (~64 tokens)

Get task status

Fetch one task, refreshing its status from the provider first. Returns status (pending/processing/completed/failed) and progress counts. Poll this after creating a task.

Input parameters:

- `task_id` (integer, required): Rapid Indexer task id (from list_tasks or a create_* result).

Output parameters:

- `bing_indexing` (boolean)
- `brave_indexing` (boolean)
- `completed_at` (string|null)
- `created_at` (string)
- `dashboard_url` (string)
- `engine` (string|null)
- `google_indexing` (boolean)
- `id` (number)
- `progress` (object)
- `status` (string)
- `title` (string|null)
- `type` (string)
- `vip` (boolean)

### `get_task_links` (~146 tokens)

Get per-URL results for a task

Return each URL in an indexing or index-check task with its status (indexed / unindexed / pending / error). Indexing tasks add crawl_status, and bing_status (waiting / crawled / stopped / error) when Bing was selected; index checks with Brave add brave_status (pending / indexed / unindexed / error). Filter by status and paginate with limit/offset for big tasks. Always includes a summary count.

Input parameters:

- `limit` (integer): Max links to return.
- `offset` (integer)
- `status` (string): Only return links with this status.
- `task_id` (integer, required): Rapid Indexer task id (from list_tasks or a create_* result).

Output parameters:

- `has_more` (boolean)
- `links` (array)
- `offset` (number)
- `returned` (number)
- `summary` (object)
- `task_id` (number)

### `create_traffic_campaign` (~338 tokens)

Create AI traffic campaign

Send 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.

Input parameters:

- `ai_enabled` (boolean): Human-like AI browsing (scrolling, reading, internal clicks).
- `bounce_rate` (integer): Percent of single-page visits.
- `click_chance` (integer): Percent of visitors who click one of click_links.
- `click_links` (array): Paths or CSS selectors the visitor may click, e.g. ["/pricing", "button.cta"].
- `country` (string): Visitor geo. WW = worldwide mix.
- `days` (integer): Spread the visitors over this many days.
- `delay_max` (integer): Max seconds on page.
- `delay_min` (integer): Min seconds on page.
- `device` (string)
- `link` (string, required): Target page the visitors should land on.
- `pages_max` (integer): Max internal pages per visit.
- `pages_min` (integer): Min internal pages per visit.
- `referrer` (string): Apparent traffic source, e.g. "facebook.com" or a full URL. Empty = direct.
- `title` (string): Campaign name shown in the dashboard.
- `video_chance` (integer)
- `visitors` (integer, required): Total visitors to send (min 30, max 1,000 per scheduled day).

Output parameters:

- `campaign_id` (string|null)
- `ctr_mode` (object)
- `dashboard_url` (string)
- `days` (number)
- `message` (string)
- `status` (string)
- `task_id` (number)
- `visitors` (number)

### `create_ctr_campaign` (~436 tokens)

Create CTR (search-and-click) campaign

Send 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.

Input parameters:

- `ai_enabled` (boolean): Human-like AI browsing (scrolling, reading, internal clicks).
- `bounce_rate` (integer): Percent of single-page visits.
- `click_chance` (integer): Percent of visitors who click one of click_links.
- `click_links` (array): Paths or CSS selectors the visitor may click, e.g. ["/pricing", "button.cta"].
- `country` (string): Visitor geo. WW = worldwide mix.
- `days` (integer): Spread the visitors over this many days.
- `delay_max` (integer): Max seconds on page.
- `delay_min` (integer): Min seconds on page.
- `device` (string)
- `keywords` (array, required): Search queries the visitors will type.
- `link` (string, required): Target page the visitors should land on.
- `pages_max` (integer): Max internal pages per visit.
- `pages_min` (integer): Min internal pages per visit.
- `referrer` (string): Apparent traffic source, e.g. "facebook.com" or a full URL. Empty = direct.
- `search_engine` (string): Engine key from list_search_engines (GOOGLE, BING, YAHOO, DUCKDUCKGO, YANDEX, BAIDU, NAVER, AMAZON, ...).
- `search_language` (string): Search UI language code.
- `search_only` (boolean): Search without clicking the result (search-volume boost only).
- `search_pages_max` (integer): How many result pages to scan for the target URL.
- `title` (string): Campaign name shown in the dashboard.
- `video_chance` (integer)
- `visitors` (integer, required): Total visitors to send (min 30, max 1,000 per scheduled day).

Output parameters:

- `campaign_id` (string|null)
- `ctr_mode` (object)
- `dashboard_url` (string)
- `days` (number)
- `message` (string)
- `status` (string)
- `task_id` (number)
- `visitors` (number)

### `list_search_engines` (~24 tokens)

List search engines for CTR campaigns

Return the search engines and marketplaces accepted by create_ctr_campaign.search_engine.

Output parameters:

- `search_engines` (object)
- `total` (number)

### `check_service_health` (~40 tokens)

Check Rapid Indexer service health

Ping the Rapid Indexer API and report version and enabled features (indexer, checker, traffic, ctr). Also validates that the configured API key works.

Output parameters:

- `api_base_url` (string)
- `features` (object)
- `status` (string)
- `version` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-rapid-indexer-mcp/mcp#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73
- 2026-10-24: 73
- 2026-10-23: 73
- 2026-10-22: 72
- 2026-10-21: 72
- 2026-10-20: 71
- 2026-10-19: 71
- 2026-10-18: 70
- 2026-10-17: 70
- 2026-10-16: 69
- 2026-10-15: 69
- 2026-10-14: 68
- 2026-10-13: 68
- 2026-10-12: 67
- 2026-10-10: 66

## Common questions

### What is the Rapid Indexer MCP server?

Rapid Indexer is an MCP server listed in the public MCP registry as com.rapid-indexer/mcp. Send new pages and backlinks to Googlebot fast, then check which URLs Google has indexed. This page covers its hosted endpoint (https://mcp.rapid-indexer.com/mcp).

### Is the Rapid Indexer MCP server safe to use?

Rapid Indexer scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Rapid Indexer MCP server expose?

Rapid Indexer exposes 12 tools: get_account, get_pricing, estimate_cost, submit_urls_for_indexing, check_index_status, and 7 more. Their descriptions and schemas cost roughly 1,988 tokens of context every time the server is loaded.

### Does the Rapid Indexer MCP server require authentication?

No. We connected to Rapid Indexer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Rapid Indexer MCP server still maintained?

Rapid Indexer is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Rapid Indexer MCP server?

VerifyMCP ran 12 checks on Rapid Indexer, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Rapid Indexer: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.rapid-indexer.com/mcp
- Authorisation metadata: https://mcp.rapid-indexer.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/rollounden/rapid-indexer-mcp
- Website: https://rapid-indexer.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-rapid-indexer-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-rapid-indexer-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-rapid-indexer-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-rapid-indexer-mcp/mcp