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