Xcatcher-X (Twitter) Scraping Remote Mcp
Remote MCP / x402 / USDC / Base / Solana / OpenAPI / Google ADK / Gemini Xcatcher is an agent-first Remote MCP server (Streamable HTTP) for high-throughput crawling of fresh/latest posts across large sets of X (Twitter) usernames. It supports x402 pay-as-you-go top-ups using USDC on Base and Solana.
README
Xcatcher MCP (Remote)
Remote MCP / x402 / USDC / Base / Solana / OpenAPI / Google ADK / Gemini
Xcatcher is an agent-first Remote MCP server (Streamable HTTP) for high-throughput crawling of fresh/latest posts across large sets of X (Twitter) usernames.
It supports x402 pay-as-you-go top-ups using USDC on Base and Solana, and ships an OpenAPI spec for direct import by agent builders.
Copy-paste quickstart (3 commands)
# 1) Google ADK end-to-end (Remote MCP + x402)
cd google-adk && python -m venv .venv && source .venv/bin/activate && pip install -r requirements.txt && \
XCAT_BASE="https://xcatcher.top" XCAT_API_KEY="xc_live_xxx" XCAT_MODE="normal" python adk_mcp_e2e.py
# 2) curl end-to-end (Remote MCP create -> 402 -> quote decode -> topup -> retry -> download)
cd curl && cp env.example .env && sed -i.bak 's/xc_live_xxx/xc_live_xxx/' .env && bash mcp_x402_e2e.sh
# 3) Quote (points -> USDC invoice) + (after you pay) topup
curl -s "https://xcatcher.top/api/v1/x402/quote?points=100" | jq .
Directory listings (discovery)
- Glama: https://glama.ai/mcp/servers/@lvpiggyqq/xcatcher-remote-mcp
- Smithery: https://smithery.ai/search?q=xcatcher
Endpoints
- Base URL:
https://xcatcher.top - Remote MCP (Streamable HTTP):
https://xcatcher.top/mcp/ - REST API base:
https://xcatcher.top/api/v1 - Docs:
https://xcatcher.top/docs/ - Health (public):
https://xcatcher.top/mcp/health
Authentication
All MCP and REST calls require:
Authorization: Bearer xc_live_...
Acquire an API key via REST:
POST /api/v1/auth/register(creates account + returnsapi_key)POST /api/v1/auth/login(returnsapi_key, may revoke older keys)
Important:
- Result files are not public direct links. Always download via authenticated endpoints using the same Bearer token.
OpenAPI import
Raw spec (copy into an agent builder / API tool):
Recommended usage:
- Import the OpenAPI spec to quickly wire REST calls (points, quote/topup, downloads).
- Use Remote MCP for tool-style orchestration (create → poll → download), especially with agent frameworks.
Output format
- Default export: XLSX
- If CSV is needed, convert the downloaded XLSX to CSV client-side.
Modes: normal vs deep
Default recommendation: normal (faster, lower latency for “latest posts” monitoring).
normal (recommended)
- Purpose: fast “latest posts” snapshot at scale
- Best for: monitoring, alerting, pipelines that repeatedly fetch new posts
deep (optional)
- Purpose: deeper per-user collection / enrichment
- Best for: deeper historical/contextual pulls where latency is less critical
Notes:
- Exact cost and remaining balance are returned by the server when you create a task (e.g.,
cost_points,balance_after).
Remote MCP tools (agent-friendly core)
Xcatcher exposes a small, agent-friendly core:
create_crawl_task(side effect: consumes points)x402_topup(side effect: credits points after on-chain payment proof)get_task_status(poll until done)get_result_download_url(returns authenticated download URL)cancel_task(cancel a queued task; policy may refund)
Agents should rely on the tool schema (tools/list) for exact input fields, constraints, and server-side validation rules.
Remote MCP JSON-RPC (cURL)
MCP is JSON-RPC over HTTP. You must include Accept: application/json.
BASE="https://xcatcher.top"
API_KEY="xc_live_xxx"
curl -sS -X POST "$BASE/mcp/" \
-H "Authorization: Bearer $API_KEY" \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | jq .
Quickstart (Google ADK → Remote MCP)
See: ./google-adk/README.md
One-liner:
cd google-adk
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
XCAT_BASE="https://xcatcher.top" XCAT_API_KEY="xc_live_xxx" XCAT_MODE="normal" python adk_mcp_e2e.py
Quickstart (REST API)
Workflow: create task → poll → download.
BASE="https://xcatcher.top"
# 1) Register -> returns api_key (xc_live_...)
curl -s -X POST "$BASE/api/v1/auth/register" \
-H "Content-Type: application/json" \
-d '{"username":"YOUR_USERNAME","password":"YOUR_PASSWORD"}'
# 2) Login -> returns api_key (may revoke old key)
curl -s -X POST "$BASE/api/v1/auth/login" \
-H "Content-Type: application/json" \
-d '{"username":"YOUR_USERNAME","password":"YOUR_PASSWORD"}'
API_KEY="xc_live_xxx"
# 3) Check points
curl -s "$BASE/api/v1/me" -H "Authorization: Bearer $API_KEY"
# 4) Create task (side-effect: consumes points; may return 402)
curl -s -X POST "$BASE/api/v1/tasks" \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{"mode":"normal","users":["elonmusk","naval"],"idempotency_key":"rest-req-001"}'
Poll + download:
BASE="https://xcatcher.top"
API_KEY="xc_live_xxx"
TASK_ID=10136
# Poll
curl -s "$BASE/api/v1/tasks/$TASK_ID" -H "Authorization: Bearer $API_KEY"
# Download (xlsx stream)
curl -L -o "task_${TASK_ID}.xlsx" \
-H "Authorization: Bearer $API_KEY" \
"$BASE/api/v1/tasks/$TASK_ID/download"
x402 Top-up (Base / Solana)
When you create a task with insufficient points, you may get HTTP 402 with a PAYMENT-REQUIRED header (base64 JSON) and a body containing a quote (quote_id, payTo, maxAmountRequired, etc.).
Practical workflow:
- Request a quote (or trigger 402 to receive one)
- Pay USDC to the returned
payTo - Paste the resulting
txHash/signatureintoPAYMENT-SIGNATURE, then top up
Minimum payment note:
- Minimum top-up is 0.5 USDC (paying less may fail verification).
PAYMENT-SIGNATURE format
Topup proof is sent as HTTP header: PAYMENT-SIGNATURE
Value = base64(UTF-8 JSON):
- Base proof uses
txHash - Solana proof uses
signature
Base example:
{
"x402Version": 1,
"scheme": "exact",
"network": "eip155:8453",
"payload": { "txHash": "0x...base_transaction_hash..." }
}
Solana example:
{
"x402Version": 1,
"scheme": "exact",
"network": "solana:mainnet",
"payload": { "signature": "5v...solana_tx_signature...pQ" }
}
Base: quote → pay USDC → topup → /me
BASE="https://xcatcher.top"
API_KEY="xc_live_xxx"
POINTS=100
# 1) Quote
curl -s "$BASE/api/v1/x402/quote?points=$POINTS" | jq .
# 2) Pay on Base:
# - send USDC to quote.accepts.base.payTo
# - amount >= quote.accepts.base.maxAmountRequired (atomic, 6 decimals)
QUOTE_ID="q_xxx"
BASE_TXHASH="0x...your_base_tx_hash..."
# 3) PAYMENT-SIGNATURE = base64(json)
PAYMENT_SIGNATURE_B64=$(jq -nc --arg tx "$BASE_TXHASH" \
'{"x402Version":1,"scheme":"exact","network":"eip155:8453","payload":{"txHash":$tx}}' \
| base64 -w 0)
# macOS fallback:
# PAYMENT_SIGNATURE_B64=$(jq -nc --arg tx "$BASE_TXHASH" \
# '{"x402Version":1,"scheme":"exact","network":"eip155:8453","payload":{"txHash":$tx}}' \
# | base64 | tr -d '\n')
# 4) Top up CURRENT key
curl -s -X POST "$BASE/api/v1/x402/topup" \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-H "PAYMENT-SIGNATURE: $PAYMENT_SIGNATURE_B64" \
-d "{\"quote_id\":\"$QUOTE_ID\"}" | jq .
# 5) Verify points
curl -s "$BASE/api/v1/me" -H "Authorization: Bearer $API_KEY" | jq .
Solana: quote → SPL transfer → topup → /me
BASE="https://xcatcher.top"
API_KEY="xc_live_xxx"
POINTS=100
# 1) Quote
curl -s "$BASE/api/v1/x402/quote?points=$POINTS" | jq .
# 2) Pay on Solana:
# - send USDC SPL to quote.accepts.solana.payTo
QUOTE_ID="q_xxx"
SOL_TX_SIG="5v...your_solana_signature...pQ"
# 3) PAYMENT-SIGNATURE = base64(json)
PAYMENT_SIGNATURE_B64=$(jq -nc --arg sig "$SOL_TX_SIG" \
'{"x402Version":1,"scheme":"exact","network":"solana:mainnet","payload":{"signature":$sig}}' \
| base64 -w 0)
# 4) Top up CURRENT key
curl -s -X POST "$BASE/api/v1/x402/topup" \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-H "PAYMENT-SIGNATURE: $PAYMENT_SIGNATURE_B64" \
-d "{\"quote_id\":\"$QUOTE_ID\"}" | jq .
# 5) Verify points
curl -s "$BASE/api/v1/me" -H "Authorization: Bearer $API_KEY" | jq .
After topup:
- Retry
create_crawl_task/POST /api/v1/tasksusing the sameidempotency_keythat triggered 402.
REST Endpoints Summary
POST /api/v1/auth/register— create account + issueapi_keyPOST /api/v1/auth/login— login + issueapi_key(may revoke older keys)GET /api/v1/me— check current user + points for Bearer keyPOST /api/v1/tasks— create a task (consumes points; returns 402 if low)GET /api/v1/tasks/<id>— read task statusGET /api/v1/tasks/<id>/download— download result file (requires Bearer)POST /api/v1/tasks/<id>/cancel— cancel queued task (policy may refund)GET /api/v1/x402/quote?points=<n>— get x402 quote by pointsPOST /api/v1/x402/topup— top up current Bearer key usingPAYMENT-SIGNATURE
Error handling (agent branching)
401 AUTH_MISSING / AUTH_INVALID: missing/invalid Bearer token402 PAYMENT_REQUIRED: pay + topup then retry (sameidempotency_key)409 RESULT_NOT_READY: keep polling429 RATE_LIMITED: back off, honorRetry-After599 UPSTREAM_UNREACHABLE: internal dependency unreachable5xx: transient errors; retry with exponential backoff
Support
- Docs: https://xcatcher.top/docs/
- Issues / requests: open an issue in this repository.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。