ColdRead
Server Details
Free signed trust report on an x402 endpoint: lint, signed offers, ERC-8004, payer mix.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- something-agent/coldread
- GitHub Stars
- 0
- Server Listing
- ColdRead
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
The three tools have clearly distinct roles: check generates a due-diligence report for an x402 seller, get_report retrieves a stored report by digest, and verify_report checks envelope integrity/signature. There is little risk of misselection because the descriptions explicitly separate report generation, retrieval, and verification.
All tools use the coldread_ prefix and snake_case, which is predictable. The only minor inconsistency is that coldread_check is a bare verb while the others follow verb_noun (get_report, verify_report), but the naming is still clear and readable.
Three tools is well-scoped for this narrow workflow: generate/check a report, retrieve a stored report, and verify its signature/integrity. Each tool has a clear reason to exist, with no redundant or filler tools.
The surface covers the core lifecycle: producing a report, fetching it later, and verifying its envelope. A discovery/listing capability for stored reports or lookup by seller identifier would be a useful minor addition, but the essential operations are present.
Available Tools
3 toolscoldread_checkColdRead checkARead-onlyInspect
Before paying an x402 seller: one signed, independent report combining a 402-challenge lint, signed-offer and signer-authorization checks, an ERC-8004 identity lookup and a labelled Base USDC payer summary over the last ~28 h. Read-only; never pays. Free.
Inputs: url (required), agent, method, pay_to.
coldread_get_reportFetch a stored ColdRead reportARead-onlyInspect
Fetch a stored signed report by its sha256 digest (reports are kept 90 days).
Inputs: digest (required).
coldread_verify_reportVerify a ColdRead reportBRead-onlyInspect
Check that a ColdRead report envelope is unmodified (JCS + sha256) and signed by a published ColdRead key. Pass the whole envelope {report, digest, signature}.
Inputs: envelope (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Trust filter for ERC-8004: only ~3.8% of x402 endpoints hit 5+ payers/30d. Free MCP; x402 upgrade.
Trust scores and on-chain payment receipts for x402 services.
Live x402 endpoint trust/diligence check before you pay it. $0.02/call via x402.
Check an x402 endpoint before your agent pays it: avoid / caution / ok, proven on-chain.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceEnables autonomous agents to inspect and audit unfamiliar x402 endpoints before spending USDC, using bounded read-only probes to surface payment challenges, pricing, network, receiver, and operational signals without signing or spending funds.-
- AlicenseAqualityCmaintenanceEnables MCP-capable agents to retrieve a tamper-evident decomposition of x402 network growth on Base and to place $399 human-reviewed endpoint or wallet audits paid over the x402 rail, without moving funds itself.3287 npmMIT
- 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
- FlicenseNot gradedqualityFmaintenanceProvides counterparty risk checks for any EVM address, returning malicious-history flags, tiered risk scoring, and plain-language summaries via x402 payment.-
Glama MCP Gateway
Add one secure layer between your agents and this server.