Skip to main content
Glama

Server Details

Check an x402 seller before paying: verdict, failure rate and evidence from paid calls on Base.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
paidfor

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation5/5

Each tool covers a distinct mode: single-seller lookup (check_x402_seller), discovery/ranking (list_reliable_sellers), a change feed (recent_changes), and a write action (report_x402_payment). The descriptions even state the triggering situations, so an agent can route cleanly. The only mild proximity is between per-seller check and the reliable-seller list, but one is targeted and the other is browse/discovery.

Naming Consistency4/5

Three of four names follow a clean verb_noun snake_case pattern (check_x402_seller, list_reliable_sellers, report_x402_payment). recent_changes breaks the convention as a bare noun phrase with no verb, which is a minor but noticeable deviation.

Tool Count4/5

Four tools is a deliberately tight surface and each one maps to a real step in the x402 payment workflow (check, discover, monitor, report). It is on the thin side — no category/filter browsing or seller detail fetch — but nothing is redundant.

Completeness4/5

The pre-payment lifecycle is well covered: verify a seller, find reliable ones, track changes, and contribute evidence with on-chain proof. Gaps are minor: no category or price-range search, no historical verdict/window queries, and no way to see the full evidence set beyond returned links.

Available Tools

4 tools
check_x402_sellerCheck an x402 seller before payingA
Read-onlyIdempotent
Inspect

Call this before any x402 payment, before retrying a request that answered HTTP 402, or whenever the user is about to buy an API call with USDC on Base or names an API they intend to pay per call. Returns a verdict (avoid, caution, ok, unknown), one sentence to act on, the seller's paid-call count and failure rate with a 95% interval, listed price, modal quote and max overcharge ratio when known, and links to the seller page and raw evidence.

Inputs: url (required). Returns: host, probe, seller, verdict, +7 more

list_reliable_sellersList reliable pay-per-call API sellersA
Read-onlyIdempotent
Inspect

Call this when choosing among sellers for a task, or when the user asks for a safe or reliable API. Returns sellers with zero failures across at least 30 paid calls, most-called first. For each: domain, category, paid-call count, the 95% upper bound on its failure rate, median quoted price in USDC, USDC paid to it in the last 30 days, when it was last seen, and its paidfor seller page.

Inputs: limit, category. Returns: sellers, generated_at

recent_changesRecent changes to x402 sellersA
Read-onlyIdempotent
Inspect

Call this when the user asks what changed, or before relying on a verdict older than a day. Returns recent changes, newest first: verdict changes, new failures by type, moved quotes, changed pay-to addresses, sellers added or reaching 30 paid calls, published seller replies, the operator-reported series maturing or disagreeing with ours. Each change has its time, type, seller domain, seller page and type-specific details (for example the old and new quote).

Inputs: host, since. Returns: count, events

report_x402_paymentReport an x402 payment outcomeA
Idempotent
Inspect

After your agent pays an x402 seller with any wallet, report what came back. Needs the resource URL, the settlement transaction hash and the outcome. Free; the report counts only with on-chain proof.

Inputs: url (required), outcome (required), tx_hash (required), http_status, +1 more. Returns: payer, pay_to, reason, status, +3 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Pay-per-call checks an AI agent runs before it moves money: token safety verdicts and wallet risk profiles on Base, on-chain payment verification, IBAN/VAT/BIC/LEI/ISIN validation, and live TLS and email-spoofing posture for a domain. Paid in USDC over x402 with no API key or account; the free payment_info tool explains the pricing.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Before an AI agent pays an x402 endpoint, checks whether it's safe to pay: liveness, scam/anomaly scan (payTo hijack, bait-and-switch, honeypot), and on-chain receiver verification. ~70% of x402 endpoints are dead or scams.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to run paid safety and data pre-checks over streamable HTTP — Base token risk and pricing, wallet balances and screening, transaction decoding, calldata and EIP-712 signature checks, ENS resolution, DNS/WHOIS, link phishing and security-header audits — with each tool call settled by an x402 USDC micropayment on Base instead of an account or API key. Also offers x402 seller preflight and web content extraction.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources