# ChainChoice published rankings (remote · chainchoice.io)

Read-only ChainChoice rankings: sourced, dated comparisons of crypto services, with evidence.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `chainchoice.io`: 71/100 (this document), [markdown](https://verifymcp.io/servers/io-chainchoice-rankings/chainchoice.md), [page](https://verifymcp.io/servers/io-chainchoice-rankings/chainchoice)

## Channel facts

- Endpoint: `https://chainchoice.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-chainchoice-rankings 'https://chainchoice.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-chainchoice-rankings": {
      "url": "https://chainchoice.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-chainchoice-rankings": {
      "type": "http",
      "url": "https://chainchoice.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-chainchoice-rankings]
url = "https://chainchoice.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-chainchoice-rankings": {
      "type": "remote",
      "url": "https://chainchoice.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-chainchoice-rankings --url 'https://chainchoice.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-chainchoice-rankings:
    url: "https://chainchoice.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-chainchoice-rankings": {
      "Transport": "http",
      "Url": "https://chainchoice.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-chainchoice-rankings -t streamable-http -u 'https://chainchoice.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-chainchoice-rankings": {
      "type": "http",
      "url": "https://chainchoice.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-04 (score 70)

First indexed and scored.

## MCP tools (7)

### `list_categories` (~39 tokens)

List the ranked categories

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.

### `get_ranking` (~93 tokens)

Get a category's published ranking

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.

Input parameters:

- `category` (string, required): A category id from list_categories, e.g. "exchange" or "hardware_wallet".
- `limit` (integer): How many rows, from the top (default 10).

### `get_ranking_for_country` (~133 tokens)

Get a category's order for one country

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.

Input parameters:

- `category` (string, required): A category id from list_categories, e.g. "exchange" or "hardware_wallet".
- `country` (string, required): ISO 3166-1 alpha-2, e.g. "DE".
- `limit` (integer): How many rows, from the top (default 10).

### `get_evidence` (~85 tokens)

Get the evidence behind a category's scores

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.

Input parameters:

- `category` (string, required): A category id from list_categories, e.g. "exchange" or "hardware_wallet".
- `product` (string): A product id from get_ranking (optional).

### `verify_receipt` (~69 tokens)

Verify a ChainChoice receipt

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.

Input parameters:

- `receipt` (object, required): The receipt JSON, with its signature.

### `search` (~289 tokens)

Search ChainChoice as a reader would

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.

Input parameters:

- `country` (string): ISO 3166-1 alpha-2, e.g. "DE" (optional).
- `query` (string, required): The words a reader would type, e.g. "kraken or coinbase" or "best exchange for a German user".

### `hand_off` (~285 tokens)

Hand a reader's decision to the provider

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.

Input parameters:

- `category` (string, required): A category id from list_categories, e.g. "exchange" or "hardware_wallet".
- `consent` (boolean, required): 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, required): 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).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-chainchoice-rankings/chainchoice#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 70

## Common questions

### 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.

## Links

- Remote endpoint: https://chainchoice.io/mcp
- Website: https://chainchoice.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-chainchoice-rankings/chainchoice.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-chainchoice-rankings/chainchoice.json
- HTML version of this page: https://verifymcp.io/servers/io-chainchoice-rankings/chainchoice