Settle Watch
Server Details
Check an x402 or MPP API before your agent pays it: uptime, price and a proven payout address.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- benmcalillycreative/x402-trust-board
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools target clearly different actors and workflows: check_listing is for sellers validating a Bazaar listing, while check_payment is for buyers validating payment safety before paying. Despite both being preflight checks, the resource and decision are distinct enough that an agent should not confuse them.
Both names follow the same verb_noun pattern with consistent snake_case: check_listing and check_payment. The convention is predictable and easy to extend or interpret.
Two tools is slightly thin for the typical 3-15 range, but the server is narrowly focused on two preflight verification workflows. Each tool has a substantial, non-overlapping role, so the small surface is reasonable rather than deficient.
The surface covers both sides of the trust problem: seller-side listing validation and buyer-side payment safety. Minor gaps exist around ongoing monitoring, historical results, or remediation, but the core preflight checks for the stated domain are present.
Available Tools
2 toolscheck_listingWhy isn't my x402 endpoint in the Bazaar?ARead-onlyInspect
For sellers: check whether an x402 endpoint is listed in Coinbase's Bazaar and, if not, why. Runs Coinbase's public validator (the indexer's own checks), looks the payout address up in Coinbase's merchant list, and adds the Settle Watch's 30-day availability against Coinbase's 99% bar for featured listings. Returns findings with a fix for each.
Inputs: url (required), method.
check_paymentCheck before paying an x402 / MPP endpointARead-onlyInspect
Before paying an agent-payable API (x402 or MPP), check whether it is safe: does it answer reliably, do its payment terms match its listing (no switched or burn wallets, no overcharges), and is the address it asks you to pay one the seller has proven is theirs. Returns verdict ok | caution | avoid | unknown with reasons. Pass the payTo address from the 402 response when you have it.
Inputs: url (required), payTo.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.
Check an x402 endpoint before your agent pays it: does it answer, what it charges, did it deliver
Check x402 endpoints before paying: liveness, price history, farm detection. Plus RU web access.
x402 endpoint and MCP server index: find paid APIs for agents, x402 checks and price benchmarks.
Related MCP Servers
- AlicenseAqualityBmaintenanceFind and vet paid x402 APIs before spending: nohumans.directory probes every listing, buys many with real USDC and records whether they delivered.4MIT
- AlicenseAqualityBmaintenanceMCP server that checks an x402 paid endpoint before an agent pays it, and checks afterwards that the receipt opens to exactly one real on-chain settlement. Two tools, no account, no API key.293 npmApache 2.0
- AlicenseNot gradedqualityCmaintenancePreflights x402 payment terms and provides an MCP server/API for checking Base USDC payments, tokens, wallets, and transactions before an agent pays.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to validate x402 endpoints and review on-chain payment evidence before relying on them, with free initial checks and automated USDC payments under configurable safety limits.36 PyPIMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.