ColdRead
REMOTE · COLDREAD.SOMETHING-AGENT.WORKERS.DEV
Free signed trust report on an x402 endpoint: lint, signed offers, ERC-8004, payer mix.
Available components
Last scanned (22 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 264 tokens (~88/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Server version: 0.1.5 → 0.1.6 functional
- 30 Oct 26 +1
- Server version: 0.1.4 → 0.1.5 functional
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.0 → 0.1.4 functional
- 28 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://coldread.something-agent.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=something-agent.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6f8d01b3f27f434c2bca9afbc694019e867 |
| SANs: *.something-agent.workers.dev, something-agent.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of coldread.something-agent.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://coldread.something-agent.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://coldread.something-agent.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
coldread_check ColdRead check ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | object | – | Optional ERC-8004 agent to check against the host |
| method | string | – | Default auto (tries both) |
| pay_to | string | – | Optional payTo you expect; a mismatch is a red flag |
| url | string | yes | The x402 endpoint URL |
No output schema declared.
No examples provided.
coldread_get_report Fetch a stored ColdRead report ~35
Fetch a stored signed report by its sha256 digest (reports are kept 90 days).
| Name | Type | Req | Description |
|---|---|---|---|
| digest | string | yes | – |
No output schema declared.
No examples provided.
coldread_verify_report Verify a ColdRead report ~54
Check that a ColdRead report envelope is unmodified (JCS + sha256) and signed by a published ColdRead key. Pass the whole envelope {report, digest, signature}.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | object | yes | – |
No output schema declared.
No examples provided.
How do I install the ColdRead MCP server?
ColdRead is a hosted endpoint at https://coldread.something-agent.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.
remote · coldread.something-agent.workers.dev
claude mcp add --transport http something-agent-coldread 'https://coldread.something-agent.workers.dev/mcp'
What is the ColdRead MCP server?
ColdRead is an MCP server listed in the public MCP registry as io.github.something-agent/coldread. Free signed trust report on an x402 endpoint: lint, signed offers, ERC-8004, payer mix. This page covers its hosted endpoint (https://coldread.something-agent.workers.dev/mcp).
Is the ColdRead MCP server safe to use?
ColdRead scores 68 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 ColdRead MCP server expose?
ColdRead exposes 3 tools: coldread_check, coldread_get_report, coldread_verify_report. Their descriptions and schemas cost roughly 219 tokens of context every time the server is loaded.
Does the ColdRead MCP server require authentication?
No. We connected to ColdRead without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ColdRead MCP server still maintained?
ColdRead is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.