ChainChoice published rankings
REMOTE · CHAINCHOICE.IO
Read-only ChainChoice rankings: sourced, dated comparisons of crypto services, with evidence.
Available components
Last scanned (5 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security80
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1084 tokens (~154/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 4 Nov 26 70
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 5 Nov 2026 · Probed https://chainchoice.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chainchoice.io | CN=YR2,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | RSA 2048 | SHA256-RSA | 5bccc609bb564dc875cc7ac5c3a12ba288b |
| SANs: chainchoice.io, www.chainchoice.io | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of chainchoice.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| chainchoice.io. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'sha256-P+Og7RVPlxhL+xmcANStuG1tWgHIMYdDUu/CcgryZP8=' 'sha256-VevY99NeqUf/WU62FN0e8k1xmjhXdfoyRMtju/c02bc=' 'sha256-X1kOQ88SkhPMCWC0GFaqQ2iy5P9HbZQOOs3fz66rc1I=' https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: https:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://api.anthropic.com https://*.supabase.co https://cloudflareinsights.com https://api.coingecko.com https://api.llama.fi https://yields.llama.fi https://*.ingest.de.sentry.io; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), attribution-reporting=(), autoplay=(), bluetooth=(), browsing-topics=(), camera=(), captured-surface-control=(), clipboard-read=(), compute-pressure=(), cross-origin-isolated=(), digital-credentials-get=(), display-capture=(), encrypted-media=(), fullscreen=(), gamepad=(), geolocation=(), gyroscope=(), hid=(), identity-credentials-get=(), idle-detection=(), interest-cohort=(), join-ad-interest-group=(), keyboard-map=(), language-detector=(), local-fonts=(), local-network=(), local-network-access=(), loopback-network=(), magnetometer=(), microphone=(), midi=(), on-device-speech-recognition=(), otp-credentials=(), payment=(), picture-in-picture=(), private-aggregation=(), private-state-token-issuance=(), private-state-token-redemption=(), publickey-credentials-create=(), publickey-credentials-get=(), run-ad-auction=(), screen-wake-lock=(), serial=(), shared-storage=(), shared-storage-select-url=(), storage-access=(), summarizer=(), translator=(), usb=(), window-management=(), xr-spatial-tracki |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://chainchoice.io/mcp | Verified | 200 | |
| http (plaintext) | http://chainchoice.io/mcp | HTTPS enforced | 308 | https://chainchoice.io/mcp |
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 →
get_evidence Get the evidence behind a category's scores ~85
For one category (and optionally one product id): each criterion, its weight, and per product the score with the quoted passage, its source URL and the day it was read.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | A category id from list_categories, e.g. "exchange" or "hardware_wallet". |
| product | string | – | A product id from get_ranking (optional). |
No output schema declared.
No examples provided.
get_ranking Get a category's published ranking ~93
The published order of one category: rank, product id, name and ChainChoice Score, with the methodology version, the dimension weights and what was assessed. The same order the category page and rankings.json publish.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | A category id from list_categories, e.g. "exchange" or "hardware_wallet". |
| limit | integer | – | How many rows, from the top (default 10). |
No output schema declared.
No examples provided.
get_ranking_for_country Get a category's order for one country ~133
The category's products as a reader in one country sees them: those available there, in order, with each one's published score and rank beside it. When nothing passes the country's availability filter, resultMode is "fallback" and the rows are the published order, none confirmed for that country.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | A category id from list_categories, e.g. "exchange" or "hardware_wallet". |
| country | string | yes | ISO 3166-1 alpha-2, e.g. "DE". |
| limit | integer | – | How many rows, from the top (default 10). |
No output schema declared.
No examples provided.
hand_off Hand a reader's decision to the provider ~285
Once the reader has agreed to go to a provider (consent: true), returns what to hand over: the provider's own address as ChainChoice's catalog records it (never a referral or affiliate link; ChainChoice earns nothing from it), the product's published rank and ChainChoice Score, the reader's country and monthly volume, the ranked list's page with that setup, whether the provider serves that country, and a receipt signed with ChainChoice's published key (check it with verify_receipt) recording exactly what was handed over. A provider that does not serve the reader's country is not handed off: handedOff is false with the reason. It does not open anything, log the reader or change any ranking.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | A category id from list_categories, e.g. "exchange" or "hardware_wallet". |
| consent | boolean | yes | true only once the reader has agreed to be sent to this provider. |
| country | string | – | The reader's country, ISO 3166-1 alpha-2, e.g. "DE" (optional). |
| product | string | yes | A product id from get_ranking or a search answer. |
| query | string | – | The reader's words, if the hand-off follows a search (optional, kept in the receipt). |
| vol | integer | – | The reader's monthly amount (optional). |
No output schema declared.
No examples provided.
list_categories List the ranked categories ~39
Every category ChainChoice ranks, with how many products it ranks, how many it assessed and left out with a reason, its leader, and its page.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search Search ChainChoice as a reader would ~289
Reads a query exactly as ChainChoice's search bars do (the same resolver as the homepage, the navigation field and the command palette) and returns that reading: the page it opens (a category's ranked list with the country, monthly volume, sort and filters read from the words, a product's verdict, a two-product compare, a guide), or the question it asks with at most three options, each with the page it opens; `answer`, the card the bars show before a page opens (the published #1 or the named product, its ChainChoice Score and rank, the margin, why it leads, its main trade-off, the list's page and a link to watch it), every figure from the published ranking; `readBy` when a model read a sentence the rules could not (only while ChainChoice's model tier is on and released by its measured eval); plus `open`, the homepage address that runs the same search. `country` applies a reader's country to a ranked list when the words name none; a country in the words wins. Nobody pays for a place in any answer.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2, e.g. "DE" (optional). |
| query | string | yes | The words a reader would type, e.g. "kraken or coinbase" or "best exchange for a German user". |
No output schema declared.
No examples provided.
verify_receipt Verify a ChainChoice receipt ~69
Checks a signed receipt (as ChainChoice serves it, or an issuer envelope) against the keys ChainChoice publishes: whether its content hash matches and its signature is valid. The same verifier as POST /api/v1/verify.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | The receipt JSON, with its signature. |
No output schema declared.
No examples provided.
How do I install the ChainChoice published rankings MCP server?
ChainChoice published rankings is a hosted endpoint at https://chainchoice.io/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 · chainchoice.io
claude mcp add --transport http io-chainchoice-rankings 'https://chainchoice.io/mcp'
What is the ChainChoice published rankings MCP server?
ChainChoice published rankings is an MCP server listed in the public MCP registry as io.chainchoice/rankings. Read-only ChainChoice rankings: sourced, dated comparisons of crypto services, with evidence. This page covers its hosted endpoint (https://chainchoice.io/mcp).
Is the ChainChoice published rankings MCP server safe to use?
ChainChoice published rankings scores 71 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 ChainChoice published rankings MCP server expose?
ChainChoice published rankings exposes 7 tools: list_categories, get_ranking, get_ranking_for_country, get_evidence, verify_receipt, and 2 more. Their descriptions and schemas cost roughly 993 tokens of context every time the server is loaded.
Does the ChainChoice published rankings MCP server require authentication?
No. We connected to ChainChoice published rankings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ChainChoice published rankings MCP server still maintained?
ChainChoice published rankings is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.