Skip to main content
Glama

Server Details

Verified agentic-commerce protocol status + merchant agent-readiness reports. Free on testnet.

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
–

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have clearly distinct roles: list_protocols browses, query_ledger searches by free text, whats_new lists recent changes, and check_agent_readiness scans a domain. The only real overlap is get_status vs get_status_detail, which target the same resource with different depth; the descriptions do draw the line explicitly (headline + one source vs. fuller answer), so an agent can choose, though it may just default to the detail variant.

Naming Consistency4/5

Five of six names follow a clean verb_noun snake_case pattern (check_agent_readiness, get_status, get_status_detail, list_protocols, query_ledger). The lone deviation is whats_new, which lacks a verb and the internal underscore, but overall the convention is predictable.

Tool Count4/5

Six tools is well within the sweet spot for a read-only ledger lookup service, and each covers a plausible lookup mode. The only mild redundancy is the get_status/get_status_detail pair, which could arguably be one tool with a detail flag.

Completeness4/5

The surface covers discovery (list_protocols, query_ledger), retrieval at two depths (get_status, get_status_detail), change tracking (whats_new), plus a domain scanner, so the core read lifecycle is closed with no write operations expected on a free testnet. Minor gaps: no filtering or pagination for list_protocols, no batch/multi-row status lookup, and only up to 3 sources per row.

Available Tools

6 tools
check_agent_readinessA
Read-onlyIdempotent
Inspect

Free on testnet. Automated scan, not human-verified. Scan-only quick read of whether AI agents can discover and buy from a website. Returns the engine's report as-is: scanner_version and scan_id ("v6"), report.score (scan-only), report.band (can be 'Partly assessed'), report.coverage, report.summary, report.confidence, report.can_agents_buy, report.who_eats_the_loss (display label "Who carries the risk?"; needs the 5 answers, so not assessed here), report.archetype ('unclassified' if not classified), report.rows (with unknown_reason), report.gaps, report.actions (always exactly 3: 2 business then 1 technical, each with kind "business" | "technical"), report.ledger (related Ledger entries), checks, evidence, findings, chatgpt_wallet (ChatGPT Wallet and cloud browser rules from OpenAI's public merchant guides: each rule is MATCH, NOT_MATCH or UNKNOWN with why, fix steps and the OpenAI source; UNKNOWN means it cannot be seen from outside; possible_block marks a block seen by our unsigned request, not proof; it does not change the score), and scan_interrupted.reason (timeout|blocked|dns_tls|robots_disallowed|refused|http_error) when the scan could not finish. Input: a bare domain (e.g. "yourstore.com"). It reads public pages only; it is NOT a certification, audit or legal advice. Open questions only the business can answer come back with a link to https://thepaymentsnotes.com/readiness. Limits: 3 scans per caller per day and 50 per day overall, shared with the website; results are cached for 24h. Weekly newsletter: https://thepaymentstack.substack.com

Inputs: domain (required).

get_statusA
Read-onlyIdempotent
Inspect

Free on testnet. Status of one Ledger row (protocol, platform, wallet or stablecoin) from the human-verified Ledger: headline, status, last verified date and ONE source URL. If the name is not in the Ledger: result="unknown" plus up to 3 did_you_mean names (never a guessed answer). Call list_protocols to see every name.

Inputs: protocol (required).

get_status_detailA
Read-onlyIdempotent
Inspect

Free on testnet (no payment, no wallet needed). Fuller answer for ONE Ledger row (protocol, platform, wallet or stablecoin): headline, status (authoritative), maturity (a plain-English stage derived from status, never contradicts it), steward, what_this_means (the detail after the headline, omitted if there is none), latest update date, verified date and up to 3 sources. Unknown names return result="unknown" with up to 3 did_you_mean names. Call list_protocols to see every name.

Inputs: protocol (required).

list_protocolsA
Read-onlyIdempotent
Inspect

Free on testnet. Every row in the human-verified Ledger (protocols, platforms, wallets, stablecoins): name, short names/aliases and status only. Use a name from here with get_status or get_status_detail.

Inputs: no named parameters.

query_ledgerA
Read-onlyIdempotent
Inspect

Free on testnet. Free-text keyword search over the human-verified Ledger (protocols, platforms, wallets, stablecoins). Returns up to 5 matching row NAMES with status, a relevance score and which fields matched (exact_name, name, steward, status, text). It returns names, not answers: call get_status or get_status_detail with a returned name for the verified headline, date and source. No match returns result="none" (never a guess). Example: {"query":"pay per API request for a data feed","limit":3} -> {"result":"found","hits":[{"name":"x402","status":"Live (Limited)","score":9.1,"matched":["text"]}, ...]}.

Inputs: query (required), limit.

whats_newA
Read-onlyIdempotent
Inspect

Free on testnet. Recent verified Ledger changes since a date (last 30 days, max 5 items): headline, status, date, one source.

Inputs: since_date (required).

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

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources