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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.