Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Xcatcher — Recent X Posts

REMOTE · XCATCHER.TOP · SCANNED SEP 20

Fetch recent public X/Twitter posts by named handle for monitoring, comparison, OSINT, and research.

Available components

0 this week 77 Trust /100

Recent critical change

Authorization (7 Aug 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security51
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1814 tokens (~106/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Xcatcher — Recent X Posts MCP server?

Xcatcher — Recent X Posts is a hosted endpoint at https://xcatcher.top/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.

remote · xcatcher.top

# add to Claude Code
claude mcp add --transport http lvpiggyqq-xcatcher 'https://xcatcher.top/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "lvpiggyqq-xcatcher": {
      "url": "https://xcatcher.top/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "lvpiggyqq-xcatcher": {
      "type": "http",
      "url": "https://xcatcher.top/mcp/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.lvpiggyqq-xcatcher]
url = "https://xcatcher.top/mcp/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lvpiggyqq-xcatcher": {
      "type": "remote",
      "url": "https://xcatcher.top/mcp/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add lvpiggyqq-xcatcher --url 'https://xcatcher.top/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  lvpiggyqq-xcatcher:
    url: "https://xcatcher.top/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "lvpiggyqq-xcatcher": {
      "Transport": "http",
      "Url": "https://xcatcher.top/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add lvpiggyqq-xcatcher -t streamable-http -u 'https://xcatcher.top/mcp/'
// mcp.json
{
  "mcpServers": {
    "lvpiggyqq-xcatcher": {
      "type": "http",
      "url": "https://xcatcher.top/mcp/"
    }
  }
}

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Sept 26 0
    • Stability: 0.97 → pass security
  • 5 Sept 26 +1

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

  • 3 Sept 26 +1

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

  • 1 Sept 26 +1

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

  • 30 Aug 26 +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.

  • 27 Aug 26 +1

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

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1

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

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://xcatcher.top/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=xcatcher.top CN=WE1,O=Google Trust Services,C=US 7 Aug 2026 5 Nov 2026 ECDSA 256 ECDSA-SHA256 d461ea32b79e465e13fab4ad6af2cafc
SANs: xcatcher.top, tg-relay.xcatcher.top, *.tg-relay.xcatcher.top
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of xcatcher.top. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
top. present 26780 8 Verified
xcatcher.top. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy default-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; connect-src 'self'; img-src 'self' data:; object-src 'none'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://xcatcher.top/mcp/ Verified 200
http (plaintext) http://xcatcher.top/mcp/ Inconclusive 406
MCP tools · 17 exposed · ~1,814 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cancel_task ~49

Cancel a queued task by task_id. Side effects: changes task state. Xcatcher refunds cost_points when a queued task is successfully cancelled.

NameTypeReqDescription
task_idintegeryesTask ID to cancel.
NameTypeReqDescription
resultobjectyes

No examples provided.

create_crawl_task ~320

Create a crawl task for one or more X (Twitter) usernames. Side effects: creates a new task AND consumes points. If points are insufficient, upstream returns HTTP 402 with PAYMENT-REQUIRED (quote). This tool surfaces it as error.code=PAYMENT_REQUIRED with payment_required payload so agents can request spending approval, top up, then retry safely. Modes: - normal: Fast latest-post snapshot at scale (fresh-feed monitoring). Optimized for high-throughput batch retrieval. - deep: Deeper per-user collection/enrichment (typically slower; higher resource usage). Use when you need more than a quick latest-post snapshot. Performance note: Normal mode is optimized for a small latest-post snapshot per handle. Actual completeness and latency depend on X availability, upstream limits, and network conditions. Batching: For very large sets, split users into batches. Suggested upper bound per task: 500 users (configurable via MAX_USERS_PER_TASK). Reliability: - Use idempotency_key to make retries safe (avoid duplicate charges). - After creation, poll get_task_status every 5–10s until has_result=true. - Then call get_result_download_url (download still requires the same Bearer token).

NameTypeReqDescription
idempotency_keyOptional idempotency key for safe retries (recommended for agents).
modestringnormal = fast latest-post snapshot at scale; deep = deeper per-user collection (slower).
usersarrayyesArray of X usernames (handles). You may include a leading '@'.
NameTypeReqDescription
resultobjectyes

No examples provided.

get_account_balance ~45

Return the account attached to the current Bearer API key and its points balance. Use before creating a task to estimate whether an x402 top-up will be needed. Read-only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultobjectyes

No examples provided.

get_direct_crawl_payment ~161

Create a request-bound x402 v2 payment requirement for an accountless crawl. Use this only for the accountless x402 path after preflight_crawl; API-key accounts use create_crawl_task instead. Normal requests use progressive batch pricing, so quote the complete deduplicated handle list together. This does not move funds. Return payment_required_b64 unchanged to an x402-compatible wallet/client; the live amount, asset, network, destination, and quoteId are authoritative.

NameTypeReqDescription
modestringDirect x402 normal requests use progressive batch pricing; deep is $0.10 per normalized requested handle. Always preflight the complete list.
usersarrayyesX handles, @handles, or x.com/twitter.com profile URLs.
NameTypeReqDescription
resultobjectyes

No examples provided.

get_direct_result_preview ~115

Return structured JSON rows for a completed accountless paid crawl. Use this instead of get_result_preview for an accountless x402 task; API-key accounts use get_result_preview. Use offset for pagination; the task token is required and should be treated as a secret.

NameTypeReqDescription
limitintegerRows to return (1-100).
offsetintegerZero-based row offset.
task_idintegeryesCompleted paid task ID.
task_tokenstringyesTask-scoped xtask_ token.
NameTypeReqDescription
resultobjectyes

No examples provided.

get_direct_task_status ~100

Read an accountless paid crawl using its task_id and task-scoped token. Use this instead of get_task_status for an accountless x402 task. Poll every 5-10 seconds until task.has_result is true or it reaches failed/cancelled.

NameTypeReqDescription
task_idintegeryesTask ID returned after x402 settlement.
task_tokenstringyesTask-scoped xtask_ token returned after settlement or idempotent recovery.
NameTypeReqDescription
resultobjectyes

No examples provided.

get_result_download_url ~75

Get an absolute download URL for a task result (read-only). If the task is not finished, returns ok=false with code=RESULT_NOT_READY (HTTP 409). Downloading the URL requires the same Authorization: Bearer token.

NameTypeReqDescription
task_idintegeryesTask ID. Must be completed (has_result=true).
NameTypeReqDescription
resultobjectyes

No examples provided.

get_result_preview ~128

Return up to 100 result rows from an API-key account task as native structured JSON for direct agent analysis; accountless x402 tasks use get_direct_result_preview instead. Use offset/next_offset for pagination; this does not download or parse XLSX. Use after has_result=true; use get_result_download_url when the complete XLSX is required. Read-only.

NameTypeReqDescription
limitintegerMaximum result rows to return (1-100).
offsetintegerZero-based row offset for pagination.
task_idintegeryesCompleted task ID owned by the current API key.
NameTypeReqDescription
resultobjectyes

No examples provided.

get_sample_result ~49

Return a stable synthetic example of Xcatcher's paginated result and coverage metadata. No live X data is fetched, no account is needed, no task or quote is created, and no funds move.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultobjectyes

No examples provided.

get_service_info ~47

Read Xcatcher's live capabilities, prices, limits, endpoints, and recommended agent workflow. Call this first when planning a crawl or when cached documentation may be stale. No points are consumed.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultobjectyes

No examples provided.

get_task_status ~85

Get API-key account task status by task_id (read-only); accountless x402 tasks use get_direct_task_status instead. Recommended polling interval: every 5–10 seconds until has_result=true. Returns safe structured state, result metadata, and authenticated result URLs; server filesystem paths are never exposed.

NameTypeReqDescription
task_idintegeryesTask ID returned by create_crawl_task.
NameTypeReqDescription
resultobjectyes

No examples provided.

get_x402_quote ~79

Create a short-lived USDC quote for a requested number of Xcatcher points. Returns the exact live amount and supported Base/Solana payment requirements; it does not move funds. Ask the user before signing or sending any payment.

NameTypeReqDescription
pointsintegeryesNumber of points to buy (1-200000). Live quote amount is authoritative.
NameTypeReqDescription
resultobjectyes

No examples provided.

list_crawl_tasks ~72

List recent tasks owned by the current Bearer API key, newest first. Use next_before_id for cursor pagination. Read-only and does not consume points.

NameTypeReqDescription
before_idCursor from next_before_id; omit for the newest tasks.
limitintegerTasks to return (1-100).
NameTypeReqDescription
resultobjectyes

No examples provided.

preflight_crawl ~120

Normalize and deduplicate X handles, validate the mode, and preview the current modeled points/USDC cost. This free read-only check requires no account, creates no quote or task, and moves no funds. Use it before requesting a live x402 payment challenge.

NameTypeReqDescription
modestringAPI-key accounts use 1 point per normal handle and 10 per deep handle; direct x402 normal requests receive progressive batch pricing shown by preflight.
usersarrayyesX handles, @handles, or x.com/twitter.com profile URLs.
NameTypeReqDescription
resultobjectyes

No examples provided.

submit_direct_crawl_payment ~130

Submit an x402 v2 PAYMENT-SIGNATURE for the exact users/mode used by get_direct_crawl_payment. This may settle USDC and create a crawl task. Call only after explicit spending approval. On success, securely save task_token: it grants task-scoped result access for seven days.

NameTypeReqDescription
modestringMust exactly match the quoted mode.
payment_signature_b64stringyesThe base64(JSON) PAYMENT-SIGNATURE produced for the accepted x402 v2 requirement.
usersarrayyesThe exact handles/profile URLs used for the payment requirement.
NameTypeReqDescription
resultobjectyes

No examples provided.

wait_for_task ~97

Poll a crawl task server-side until it has a result, reaches a terminal failure/cancelled state, or the bounded timeout expires. Read-only and cheaper for agent context than repeated manual polling.

NameTypeReqDescription
poll_interval_secondsintegerSeconds between status checks (2-15).
task_idintegeryesTask ID returned by create_crawl_task.
timeout_secondsintegerMaximum wait in seconds (5-120).
NameTypeReqDescription
resultobjectyes

No examples provided.

x402_topup ~142

Top up points for the CURRENT Bearer key using x402 proof. Inputs: - quote_id: returned by PAYMENT-REQUIRED (or /api/v1/x402/quote) - payment_signature_b64: base64(JSON) that will be passed as HTTP header PAYMENT-SIGNATURE Side effects: credits points to the same Bearer key (no key rotation). On success returns credited_points and balance_after (shape depends on upstream).

NameTypeReqDescription
payment_signature_b64stringyesBase64(JSON) for header PAYMENT-SIGNATURE.
quote_idstringyesQuote ID returned by PAYMENT-REQUIRED (or /x402/quote).
NameTypeReqDescription
resultobjectyes

No examples provided.

Common questions

What is the Xcatcher — Recent X Posts MCP server?

Xcatcher — Recent X Posts is an MCP server listed in the public MCP registry as io.github.lvpiggyqq/xcatcher. Fetch recent public X/Twitter posts by named handle for monitoring, comparison, OSINT, and research. This page covers its hosted endpoint (https://xcatcher.top/mcp/).

Is the Xcatcher — Recent X Posts MCP server safe to use?

Xcatcher — Recent X Posts scores 77 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 Xcatcher — Recent X Posts MCP server expose?

Xcatcher — Recent X Posts exposes 17 tools: get_service_info, preflight_crawl, get_sample_result, get_account_balance, list_crawl_tasks, and 12 more. Their descriptions and schemas cost roughly 1,814 tokens of context every time the server is loaded.

Does the Xcatcher — Recent X Posts MCP server require authentication?

No. We connected to Xcatcher — Recent X Posts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Xcatcher — Recent X Posts MCP server still maintained?

Xcatcher — Recent X Posts is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.