Rapid Indexer

com.rapid-indexerv0.1.0更新於 Oct 8, 2026

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

已驗證Streamable HTTP可網頁執行Web Search & ScrapingBusiness & Commerce

概覽

AI 產生的概覽

讓助理把網址提交給 Googlebot 以加快收錄、檢查頁面是否已被 Google 收錄,並執行流量或 CTR 活動。

功能
每個收錄任務最多可向 Googlebot 提交 10,000 個網址,可選標準或 VIP 佇列以及滴灌式投放,並建立收錄檢查任務,依網址回報已收錄或未收錄。也可列出任務、重新整理任務進度,並依狀態篩選與分頁回傳每個網址的結果。帳戶、價格與費用估算工具會回報額度餘額以及一批網址的花費,方便在消費前評估。活動工具可建立 AI 流量活動,以及讓訪客在指定搜尋引擎搜尋關鍵字並點擊結果頁的 CTR 活動。
適用情境
適合在發布或更新頁面後希望盡快被抓取,或需要確認 Google 實際收錄了哪些網址時使用。也適合在提交批量網址前估算收錄成本,或為某個網址執行流量與 CTR 活動。index_and_verify 提示會引導完成估算、提交與驗證流程。
執行需求
需要 Rapid Indexer 帳戶與 API 金鑰,可從帳戶的 API Access 頁面取得。託管端點為 Authorization 標頭中。本機執行需要 Node.js 20 以上版本以及 rapid-indexer-mcp npm 套件,金鑰放在 RAPID_INDEXER_API_KEY 中。需要能連線至 Rapid Indexer API 的網路。
安裝前請注意
需要 Rapid Indexer API 金鑰,以 Authorization 標頭(Bearer)或 RAPID_INDEXER_API_KEY 傳入,應視為機密。多個工具會消耗帳戶額度:submit_urls_for_indexing、check_index_status(約每個 URL 0.1 額度)、create_traffic_campaign 與 create_ctr_campaign,費用可能累積。流量與 CTR 活動會產生人工訪客與點擊,可能與搜尋引擎政策衝突。伺服器會把你的 URL 與帳戶資料傳送給 Rapid Indexer API。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Rapid Indexer,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

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

README

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):

json
{
  "mcpServers": {
    "rapid-indexer": {
      "command": "npx",
      "args": ["-y", "rapid-indexer-mcp"],
      "env": { "RAPID_INDEXER_API_KEY": "YOUR_API_KEY" }
    }
  }
}

Claude Desktop

~/.config/Claude/claude_desktop_config.json on Linux:

json
{
  "mcpServers": {
    "rapid-indexer": {
      "command": "npx",
      "args": ["-y", "rapid-indexer-mcp"],
      "env": { "RAPID_INDEXER_API_KEY": "YOUR_API_KEY" }
    }
  }
}

Claude Code

bash
claude mcp add rapid-indexer -e RAPID_INDEXER_API_KEY=YOUR_API_KEY -- npx -y rapid-indexer-mcp

From a local checkout (before publishing to npm)

bash
cd mcp
npm install
npm run build

Then point the host at the built CLI:

json
{
  "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.

bash
RAPID_INDEXER_BASE_URL=https://rapid-indexer.com \
node dist/cli.js --http --host 0.0.0.0 --port 3333 --path /mcp

Clients connect to https://your-host/mcp and send Authorization: Bearer <api key> (also accepted: X-API-Key: <key>, or ?api_key= on the URL). GET /healthz returns a liveness JSON.

Cursor example for a remote server:

json
{
  "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 / RAPID_INDEXER_API_KEY in HTTP mode is only a fallback for requests that carry no key (single-tenant self-hosting).

Tools

ToolSpends creditsWhat it does
get_accountnoAccount id, email, credit balance (+ USD).
get_pricingnoLive credits per URL (standard / VIP / checker), traffic price per 1,000 visitors, USD per credit.
estimate_costnoCost of N URLs as indexer/checker (+VIP) and whether the balance covers it.
submit_urls_for_indexingyesCreate an indexing task (standard or VIP queue, optional drip feed). Max 10,000 URLs.
check_index_statusyes (~0.1 cr/URL)Create an index-check task: per-URL indexed / unindexed.
list_tasksnoPaginated task list with indexed/unindexed/pending/error counts; filter by type/status.
get_tasknoRefresh and return one task's status and progress.
get_task_linksnoPer-URL results with status filter and pagination.
create_traffic_campaignyesAI visitors to a URL (geo, device, referrer, behaviour).
create_ctr_campaignyesVisitors search keywords on Google/Bing/… and click your result.
list_search_enginesnoValid search_engine values for CTR campaigns.
check_service_healthnoAPI version, enabled features, and confirms the key works.

Every tool returns human-readable text plus structuredContent validated by an output schema. Errors from the API come back as isError results with the API message and a hint (top-up link on insufficient credits, key location on 401).

Prompt: index_and_verify — guided estimate → submit → verify workflow.

Environment / flags

VariableFlagDefaultNotes
RAPID_INDEXER_API_KEY--api-key–Required for stdio. Fallback only in HTTP mode.
RAPID_INDEXER_BASE_URL--base-urlhttps://rapid-indexer.com/api/v1/index.phpSite origin is also accepted; the router path is appended.
HOST--host127.0.0.1HTTP mode.
PORT--port3333HTTP mode.
MCP_PATH--path/mcpHTTP mode.

Development

bash
npm install
npm run build          # tsc → dist/
npm run dev            # run src/cli.ts with tsx (stdio)
npm run inspect        # MCP Inspector against dist/cli.js

If npm install hangs on a machine with broken IPv6, run it with NODE_OPTIONS="--no-network-family-autoselection --dns-result-order=ipv4first".

Publishing

bash
npm version patch
npm publish --access public

prepublishOnly builds dist/. The package ships only dist/, README.md and LICENSE.

API coverage

The server talks to the public REST API documented at https://rapid-indexer.com/api-docs. list_tasks and pricing were added to that API together with this server; hosts running an older build of the site will see those two tools fail with "Invalid action" until the API is redeployed.

License

MIT

來源:README.md,提交 c314719

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v0.1.0最新Oct 8, 2026