# Verified x402 Catalog (remote · verified-catalog-lookup.withgrokbot.workers.dev)

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

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-08

## Components

- remote · `verified-catalog-lookup.withgrokbot.workers.dev`: 61/100 (this document), [markdown](https://verifymcp.io/servers/withgrokbot-verified-catalog/verified-catalog-lookup.md), [page](https://verifymcp.io/servers/withgrokbot-verified-catalog/verified-catalog-lookup)

## Channel facts

- Endpoint: `https://verified-catalog-lookup.withgrokbot.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-08.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http withgrokbot-verified-catalog 'https://verified-catalog-lookup.withgrokbot.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "withgrokbot-verified-catalog": {
      "url": "https://verified-catalog-lookup.withgrokbot.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "withgrokbot-verified-catalog": {
      "type": "http",
      "url": "https://verified-catalog-lookup.withgrokbot.workers.dev/mcp"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add withgrokbot-verified-catalog --url 'https://verified-catalog-lookup.withgrokbot.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  withgrokbot-verified-catalog:
    url: "https://verified-catalog-lookup.withgrokbot.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "withgrokbot-verified-catalog": {
      "Transport": "http",
      "Url": "https://verified-catalog-lookup.withgrokbot.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add withgrokbot-verified-catalog -t streamable-http -u 'https://verified-catalog-lookup.withgrokbot.workers.dev/mcp'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-08 (score 61, +1)

- [security] Tool “endpoint_spot_check” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 136 → 276
- [functional improvement] Tool coverage: 80% → 100%
- [functional] Schema quality: good → excellent
- [functional] Server version: 0.6.2 → 0.6.3

### 2026-10-06 (score 60, +1)

- [functional regression] Schema quality: 413 → 684
- [functional improvement] Tool coverage: 75% → 80%
- [functional] Server version: 0.5.0 → 0.6.0
- [functional] New tool “endpoint_spot_check”

### 2026-10-04 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-03 (score 59)

First indexed and scored.

## MCP tools (5)

### `search_catalog` (~382 tokens)

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.

Input parameters:

- `category` (string): Optional. Case-insensitive substring of the service category, e.g. "web search", "news", "on-chain data", "weather", "public records", "utility".
- `limit` (integer): Optional. Maximum number of results, 1-100 (default 20).
- `max_price_usd` (number): Optional. Keep services whose advertised price per call is at or below this many USD, e.g. 0.01.
- `query` (string): 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_only` (boolean): Optional (default false). If true, keep only services that were reachable in the latest check.

### `get_service` (~224 tokens)

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 ...".

Input parameters:

- `id` (string, required): Exact, case-sensitive catalog service id as returned by search_catalog or lookup, e.g. "exa-search", "x402tap-weather", "onesource-erc20-balance".

### `lookup` (~488 tokens)

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.

Input parameters:

- `endpoint` (string): 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.
- `limit` (integer): Optional. Maximum ranked services in results, 1-20 (default 10; clamped). facts_only is not limited.
- `max_price_usd` (number): Optional. Only services whose listed price per call is at or below this many USD, e.g. 0.01. Negative values are rejected.
- `n` (integer): Optional. Most recent paid receipts per service used for pass_rate and returned, 1-20 (default 5; out-of-range values are clamped).
- `payer` (string): 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.
- `task` (string): 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…

### `get_overnight_cos_pack` (~111 tokens)

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.

### `endpoint_spot_check` (~177 tokens)

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.

Input parameters:

- `claimed_price` (number): optional claimed USD price to compare vs quoted
- `task` (string): optional task label (ignored in decision output)
- `url` (string, required): public http(s) URL to probe

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/withgrokbot-verified-catalog/verified-catalog-lookup#diagnostics

## Score history

- 2026-10-08: 61
- 2026-10-06: 60
- 2026-10-04: 59
- 2026-10-03: 59

## 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.

## Links

- Remote endpoint: https://verified-catalog-lookup.withgrokbot.workers.dev/mcp
- Repository: https://github.com/withgrokbot/verified-catalog
- Website: https://withgrokbot.github.io/verified-catalog/
- Changelog RSS feed: https://verifymcp.io/servers/withgrokbot-verified-catalog/verified-catalog-lookup.xml
- Changelog JSON feed: https://verifymcp.io/servers/withgrokbot-verified-catalog/verified-catalog-lookup.json
- HTML version of this page: https://verifymcp.io/servers/withgrokbot-verified-catalog/verified-catalog-lookup