Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Xcatcher — Recent X Posts is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
17
tools declared
remote
at its publisher
—
calls last 7d
What it does
Fetch recent public X/Twitter posts by named handle for monitoring, comparison, OSINT, and research.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http xcatcher-recent-x-posts-mcp https://xcatcher.top/mcp/
# 2 — ask your agent for something these tools do
# get_service_info, preflight_crawl, get_sample_result and 14 more
Xcatcher — Recent X Posts costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LVAll 1 server
lvpiggyqq1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http xcatcher-recent-x-posts-mcp https://xcatcher.top/mcp/Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — some of its tools take a key of its publisher’s own, and the rest work without.
What it asks of you
Nothing is required, but it can take Authorization header (Optional Xcatcher API key for account tools. Discovery and direct x402 tools work without it.), Accept header (Request JSON responses from the stateless Remote MCP server.) if you want to set them. Its publisher says some of its tools need one of them, and the rest work without.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| users | array | yes | X handles, @handles, or x.com/twitter.com profile URLs. |
| mode | string | no | API-key accounts use 1 point per normal handle and 10 per deep handle; direct x402 normal requests receive progressive batch pricing shown by preflight. |
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Tasks to return (1-100). |
| before_id | no | Cursor from next_before_id; omit for the newest tasks. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| points | integer | yes | Number of points to buy (1-200000). Live quote amount is authoritative. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| users | array | yes | X handles, @handles, or x.com/twitter.com profile URLs. |
| mode | string | no | Direct x402 normal requests use progressive batch pricing; deep is $0.10 per normalized requested handle. Always preflight the complete list. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| users | array | yes | The exact handles/profile URLs used for the payment requirement. |
| payment_signature_b64 | string | yes | The base64(JSON) PAYMENT-SIGNATURE produced for the accepted x402 v2 requirement. |
| mode | string | no | Must exactly match the quoted mode. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | integer | yes | Task ID returned after x402 settlement. |
| task_token | string | yes | Task-scoped xtask_ token returned after settlement or idempotent recovery. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | integer | yes | Completed paid task ID. |
| task_token | string | yes | Task-scoped xtask_ token. |
| limit | integer | no | Rows to return (1-100). |
| offset | integer | no | Zero-based row offset. |
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 sca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| users | array | yes | Array of X usernames (handles). You may include a leading '@'. |
| mode | string | no | normal = fast latest-post snapshot at scale; deep = deeper per-user collection (slower). |
| idempotency_key | no | Optional idempotency key for safe retries (recommended for agents). |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | Quote ID returned by PAYMENT-REQUIRED (or /x402/quote). |
| payment_signature_b64 | string | yes | Base64(JSON) for header PAYMENT-SIGNATURE. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | integer | yes | Task ID returned by create_crawl_task. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | integer | yes | Task ID returned by create_crawl_task. |
| timeout_seconds | integer | no | Maximum wait in seconds (5-120). |
| poll_interval_seconds | integer | no | Seconds between status checks (2-15). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | integer | yes | Completed task ID owned by the current API key. |
| limit | integer | no | Maximum result rows to return (1-100). |
| offset | integer | no | Zero-based row offset for pagination. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | integer | yes | Task ID. Must be completed (has_result=true). |
Cancel a queued task by task_id. Side effects: changes task state. Xcatcher refunds cost_points when a queued task is successfully cancelled.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | integer | yes | Task ID to cancel. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Xcatcher — Recent X Posts or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 3.1.0 · scanned 23 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestb244bcf745192f3a863db1a3d535b491c63349385eb210599e21eab09e1e0a34
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_service_info | untrusted-input | untrusted-input: keyword "crawl" |
| preflight_crawl | untrusted-input | untrusted-input: keyword "crawl" |
| get_sample_result | no tags | |
| get_account_balance | no tags | |
| list_crawl_tasks | untrusted-input | untrusted-input: keyword "crawl" |
| get_x402_quote | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_direct_crawl_payment | untrusted-inputexternal-sink | untrusted-input: keyword "crawl"; external-sink: declares readOnlyHint: false, openWorldHint: true |
| submit_direct_crawl_payment | untrusted-inputexternal-sink | untrusted-input: keyword "crawl"; external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| get_direct_task_status | untrusted-input | untrusted-input: keyword "crawl" |
| get_direct_result_preview | untrusted-input | untrusted-input: keyword "crawl" |
| create_crawl_task | untrusted-inputexternal-sink | untrusted-input: keyword "crawl"; external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| x402_topup | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| get_task_status | no tags | |
| wait_for_task | untrusted-input | untrusted-input: keyword "crawl" |
| get_result_preview | no tags | |
| get_result_download_url | untrusted-input | untrusted-input: keyword "download" |
| cancel_task | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestb244bcf745192f3a
Scanned2026-10-23
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 3.1.0.
3.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Xcatcher — Recent X Posts can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.