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.

Verified x402 Catalog

REMOTE · VERIFIED-CATALOG-LOOKUP.WITHGROKBOT.WORKERS.DEV · SCANNED OCT 8

Which x402 pay-per-call endpoint delivered for a task at a price? Facts from our own paid calls.

61 Trust /100
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 Security46
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1382 tokens (~276/item across 5 items; 5 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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 Verified x402 Catalog MCP server?

Verified x402 Catalog is a hosted endpoint at https://verified-catalog-lookup.withgrokbot.workers.dev/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 · verified-catalog-lookup.withgrokbot.workers.dev

# add to Claude Code
claude mcp add --transport http withgrokbot-verified-catalog 'https://verified-catalog-lookup.withgrokbot.workers.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "withgrokbot-verified-catalog": {
      "url": "https://verified-catalog-lookup.withgrokbot.workers.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "withgrokbot-verified-catalog": {
      "type": "http",
      "url": "https://verified-catalog-lookup.withgrokbot.workers.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.withgrokbot-verified-catalog]
url = "https://verified-catalog-lookup.withgrokbot.workers.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "withgrokbot-verified-catalog": {
      "type": "remote",
      "url": "https://verified-catalog-lookup.withgrokbot.workers.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add withgrokbot-verified-catalog --url 'https://verified-catalog-lookup.withgrokbot.workers.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  withgrokbot-verified-catalog:
    url: "https://verified-catalog-lookup.withgrokbot.workers.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "withgrokbot-verified-catalog": {
      "Transport": "http",
      "Url": "https://verified-catalog-lookup.withgrokbot.workers.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add withgrokbot-verified-catalog -t streamable-http -u 'https://verified-catalog-lookup.withgrokbot.workers.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "withgrokbot-verified-catalog": {
      "type": "http",
      "url": "https://verified-catalog-lookup.withgrokbot.workers.dev/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.

  • 8 Oct 26 +1
    • Tool “endpoint_spot_check” rewrote its description, which is the text the model reads security
    • Schema quality: 136 → 276 ▼ functional
    • Tool coverage: 80% → 100% ▲ functional
    • Schema quality: good → excellent functional
    • Server version: 0.6.2 → 0.6.3 functional
  • 6 Oct 26 +1
    • Schema quality: 413 → 684 ▼ functional
    • Tool coverage: 75% → 80% ▲ functional
    • Server version: 0.5.0 → 0.6.0 functional
    • New tool “endpoint_spot_check” functional
  • 4 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 3 Oct 26 59

    First indexed and scored.

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 8 Oct 2026 · Probed https://verified-catalog-lookup.withgrokbot.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=withgrokbot.workers.dev CN=YE2,O=Let's Encrypt,C=US 30 Sept 2026 29 Dec 2026 ECDSA 256 ECDSA-SHA384 55585ba8a6c5b3aabcdcdae2db158c20de8
SANs: *.withgrokbot.workers.dev, withgrokbot.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of verified-catalog-lookup.withgrokbot.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://verified-catalog-lookup.withgrokbot.workers.dev/mcp Verified 200
http (plaintext) http://verified-catalog-lookup.withgrokbot.workers.dev/mcp Inconclusive 405
MCP tools · 5 exposed · ~1,382 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
endpoint_spot_check ~177

Decision-shaped SSRF-safe spot-check of a public URL for an x402 PAYMENT-REQUIRED / 402 challenge. Returns only verdict (pay|skip|recheck), reason, quoted_price_usd, claimed_price_usd, and access. Never pays the target (probe GET only). 1 free check per client per UTC day (client=vc-mcp), then $0.01 to $0.25 USDC (one tenth of the target's quoted price) on Base via x402. Unpaid after free quota: payment instructions. Forward PAYMENT-SIGNATURE for a paid check.

NameTypeReqDescription
claimed_pricenumber–optional claimed USD price to compare vs quoted
taskstring–optional task label (ignored in decision output)
urlstringyespublic http(s) URL to probe

No output schema declared.

No examples provided.

get_overnight_cos_pack ~111

Buy and download the Overnight Chief of Staff Setup Pack ($9 USDC on Base via x402): 5 ready-to-paste bot prompts, an HTML morning-briefing template, and a PDF setup guide. Always paid — no free quota. Call without PAYMENT-SIGNATURE to receive payment requirements and the HTTP endpoint URL. Agents pay by retrying the HTTP endpoint (or this MCP call) with a PAYMENT-SIGNATURE header holding a signed USDC EIP-3009 authorization.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_service ~224

Fetch the complete catalog record for one known service id (e.g. from search_catalog or lookup results). Use search_catalog to find ids and lookup to rank services for a task; get_service has no per-call receipts, so for receipts with tx and Basescan links call lookup with endpoint=<id>. Read-only. No auth or API key; free, no quota (reads the same catalog snapshot as search_catalog). Returns the record as published: id, name, provider, category, description, endpoint, advertised_price (USD, atomic, asset, network), sample_request, tasks, quality_test (known-answer test, facts_only flag and reason), paid_receipts (count), latest (full last check incl. x402_challenge, error, raw_log_url), history_summary and page_url. Unknown or missing id: error "no service with id ...".

NameTypeReqDescription
idstringyesExact, case-sensitive catalog service id as returned by search_catalog or lookup, e.g. "exa-search", "x402tap-weather", "onesource-erc20-balance".

No output schema declared.

No examples provided.

lookup ~488

Rank x402 endpoints for a known task at or under a price: "which endpoint should I pay for task X at <= $Y?". Prefer it over search_catalog (keyword browsing, unranked) and get_service (one id's raw record). No auth or API key. Calls the hosted lookup service as client=vc-mcp; all MCP users share that client's 5 free lookups per UTC day (reset 00:00 UTC), after which the tool returns an error reporting the HTTP 402 ($0.02 USDC on Base via x402) and never pays. Returns results sorted by known-answer pass_rate over the last n paid calls, then price, each with price_usd, pass_rate, last_check_at, last_check, stale and receipts (time, tx, basescan_url, charged_usd, delivered, quality); seller-broken services come unsorted under facts_only. No match: empty results, matched 0. Needs task or endpoint; invalid params return an error. Payment never changes results.

NameTypeReqDescription
endpointstring–A catalog service id (e.g. exa-search) or endpoint URL, to get one service's receipts instead of a whole task. Required unless task is given; can be combined with task.
limitinteger–Optional. Maximum ranked services in results, 1-20 (default 10; clamped). facts_only is not limited.
max_price_usdnumber–Optional. Only services whose listed price per call is at or below this many USD, e.g. 0.01. Negative values are rejected.
ninteger–Optional. Most recent paid receipts per service used for pass_rate and returned, 1-20 (default 5; out-of-range values are clamped).
payerstring–Optional 0x wallet address (40 hex characters), recorded so a later payment from it to a returned vendor can be matched on-chain. Nothing is charged; a malformed address returns an error.
taskstring–Task name from /v1/tasks, e.g. web-search, crypto-news, news, weather, token-balance, sec-filings, fx-rates, url-check. Case-insensitive; a known name matches exactly, an unknown one falls back to ma…

No output schema declared.

No examples provided.

search_catalog ~382

Browse or keyword-search the verified catalog of pay-per-call (x402) agent services. Use it when you don't know the task name or want to see what exists; use lookup to rank endpoints for a known task at a max price, and get_service for one id's full record. Read-only. No auth or API key; free, no quota or per-client limit: it only reads the catalog snapshot (bundled catalog.json in the local server, the published catalog.json on remote /mcp). Returns {count, results, generated_at, note, methodology_url}; results are in catalog order, ungraded, each with id, name, category, endpoint, advertised_price_usd, page_url and latest (checked_at, reachable, http_status, latency_ms, quoted_price_usd, price_matches_listing, charged_price_usd, delivered_valid, raw_log_url). No match: count 0, empty results. A non-numeric max_price_usd or limit returns an error.

NameTypeReqDescription
categorystring–Optional. Case-insensitive substring of the service category, e.g. "web search", "news", "on-chain data", "weather", "public records", "utility".
limitinteger–Optional. Maximum number of results, 1-100 (default 20).
max_price_usdnumber–Optional. Keep services whose advertised price per call is at or below this many USD, e.g. 0.01.
querystring–Optional. Space-separated words; every word must appear (case-insensitive) in the service id, name, category, description or provider. Omit to list all. Examples: "search", "crypto news".
reachable_onlyboolean–Optional (default false). If true, keep only services that were reachable in the latest check.

No output schema declared.

No examples provided.

Common questions

What is the Verified x402 Catalog MCP server?

Verified x402 Catalog is an MCP server listed in the public MCP registry as io.github.withgrokbot/verified-catalog. Which x402 pay-per-call endpoint delivered for a task at a price? Facts from our own paid calls. This page covers its hosted endpoint (https://verified-catalog-lookup.withgrokbot.workers.dev/mcp).

Is the Verified x402 Catalog MCP server safe to use?

Verified x402 Catalog scores 61 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 Verified x402 Catalog MCP server expose?

Verified x402 Catalog exposes 5 tools: search_catalog, get_service, lookup, get_overnight_cos_pack, endpoint_spot_check. Their descriptions and schemas cost roughly 1,382 tokens of context every time the server is loaded.

Does the Verified x402 Catalog MCP server require authentication?

No. We connected to Verified x402 Catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Verified x402 Catalog MCP server still maintained?

Verified x402 Catalog is still listed as active in the MCP registry. We last reached this channel on 8 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.