# OpenChainBench (remote · openchainbench.com)

Live, neutral benchmarks for public RPC latency, oracles, bridges, perp DEX, and prediction markets.

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `openchainbench.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/flotapponnier-openchainbench/api-mcp-mcp.md), [page](https://verifymcp.io/servers/flotapponnier-openchainbench/api-mcp-mcp)

## Channel facts

- Endpoint: `https://openchainbench.com/api/mcp/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 5956 tokens (~62/item across 96 items; 3 tools + 93 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http flotapponnier-openchainbench https://openchainbench.com/api/mcp/mcp
```

### Codex

```toml
[mcp_servers.flotapponnier-openchainbench]
url = "https://openchainbench.com/api/mcp/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "flotapponnier-openchainbench": {
      "type": "remote",
      "url": "https://openchainbench.com/api/mcp/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add flotapponnier-openchainbench --url https://openchainbench.com/api/mcp/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  flotapponnier-openchainbench:
    url: "https://openchainbench.com/api/mcp/mcp"
```

### Other

```json
{
  "mcpServers": {
    "flotapponnier-openchainbench": {
      "type": "http",
      "url": "https://openchainbench.com/api/mcp/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-08-03 (score 71, +1)

- [functional] Schema quality: good → excellent

### 2026-08-01 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 69, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 70, +2)

- [functional] Schema quality: good → excellent

### 2026-07-28 (score 68, +1)

- [functional regression] Resource “Fastest cross-chain messaging protocol, live end-to-end delivery latency · Bridges” was removed

### 2026-07-27 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 67)

First indexed and scored.

## MCP tools (3)

### `list_benchmarks` (~123 tokens)

List OpenChainBench benchmarks

Returns a flat index of every published OpenChainBench benchmark with its
current headline value, leader, category, units, and citation URL.

Call this first when the user asks a discovery question like
"what benchmarks does OpenChainBench have?" or "compare crypto aggregators".
Then use `get_benchmark` for the specific slug(s) the answer needs.

Returns one line per bench:
  { slug, title, category, metric, unit, value, leader, headline, url, asOf }

Drafts are filtered out: only live benchmarks appear.

### `get_benchmark` (~350 tokens)

Get a single OpenChainBench benchmark

Returns full detail for one benchmark, ready to cite verbatim:
  • rankings (every provider sorted by p50)
  • sparkline (24h trend, 72 points)
  • headline sentence + paste-ready citation quote
  • methodology bullets + source-code URL + canonical pageUrl + OG image URL

Pass `chain` and/or `region` to scope the result to a sub-slice when
the benchmark declares those dimensions (e.g. aggregator-head-lag
exposes chain=base|bnb|solana, region=us-east|eu-west|ap-southeast).
Both args are optional; omit them for the global aggregate.

Example usage:
  • User: "who's the fastest crypto data aggregator on Base?"
    → get_benchmark({ slug: "aggregator-head-lag", chain: "base" })
  • User: "how much does it cost to bridge $300 cross-chain?"
    → get_benchmark({ slug: "bridge-fee" })

Drafts return { error: "unknown_slug" }. Cite the returned `pageUrl`
and use `quote` as the attribution line in your answer.

Input parameters:

- `chain` (string): Optional chain filter, e.g. 'base', 'solana', 'bnb'. Only honored when the bench declares chain dimensions.
- `region` (string): Optional region filter, e.g. 'us-east', 'eu-west', 'ap-southeast'. Only honored when the bench declares region dimensions.
- `slug` (string, required): Benchmark slug from list_benchmarks. e.g. 'aggregator-head-lag', 'bridge-quote-latency', 'l1-finality'.

### `query_prom` (~621 tokens)

Run a PromQL query (scoped to benchmark metric namespaces)

Direct PromQL passthrough for advanced questions that don't map cleanly
to `list_benchmarks` / `get_benchmark`, e.g. "what was Mobula's p50
head-lag yesterday at 14:00 UTC" or "plot bridge fees over the last hour".

Prefer the higher-level tools first; reach for this when you need:
  • a custom time window (instant query at a specific point, or range)
  • a derived metric (rates, ratios, deltas)
  • a histogram bucket aggregation across chains/regions

Allowed metric namespaces (one prefix per OCB bench family):
  head_lag_seconds (aggregator latency)
  bridge_quote_latency_ms*, bridge_cost*, bridge_fees*, bridge_fix_fee*,
    bridge_gas*, bridge_output*, bridge_estimated_time*, bridge_quote_success
  l1_finality_*, l2_block_time_*
  metadata_coverage_*, metadata_api_latency_*, network_coverage_*,
    networks_supported, wallet_labels_*
  perp_fees_*, perp_funding_*, perp_venue_*, perp_execution_*,
  ocb_buyback_*, ocb_oracle_*, ocb_validator_*, ocb_chain_*
  gas_error_*, gas_predicted_*, gas_realized_*, gas_oracle_*
  peg_* (stablecoin peg, both variants)
  solana_landing_* (TX landing observational + active)
  rpc_latency_*, rpc_call_total, rpc_health, rpc_archive_depth_supported
  relay_*, per_swap_margin_usd (bridge revenue)
Queries referencing other metrics (operational/internal ones like `up`,
\`scrape_*`, `process_*`, `go_*`, `wallet_balance_*` or any label-
enumeration shape) are refused with `{error, reason}`.

Example: instant p50 over 1h for Mobula head-lag on Base:
  query_prom({
    query: "quantile_over_time(0.5, head_lag_seconds{aggregator=\"mobula\",chain=\"base\"}[1h]) * 1000"
  })

Example: 7-day sparkline of average bridge fees:
  query_prom({
    query: "avg_over_time(bridge_fees_percent[1d])",
    windowSec: 604800,
    steps: 168
  })

Returns: `{ query, value }` for instant queries, `{ query, windowSec, series }` for range.

Input parameters:

- `query` (string, required): PromQL expression referencing published benchmark metric prefixes only. Function names, label keys, and quoted label values are fine; bare metric names must be allowlisted.
- `steps` (integer): Number of samples for a range query (2 to 360). Default 60. Step duration = windowSec / steps.
- `windowSec` (integer): If set, run a range query over the last N seconds (max 7 days = 604800). Omit for an instant query.

## Diagnostics

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

## Score history

- 2026-08-03: 71
- 2026-08-02: 70
- 2026-08-01: 70
- 2026-07-31: 69
- 2026-07-30: 70
- 2026-07-28: 68
- 2026-07-27: 67
- 2026-07-26: 67

## Links

- Remote endpoint: https://openchainbench.com/api/mcp/mcp
- Repository: https://github.com/ChainBench/OpenChainBench
- Website: https://openchainbench.com/
- Changelog RSS feed: https://verifymcp.io/servers/flotapponnier-openchainbench/api-mcp-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/flotapponnier-openchainbench/api-mcp-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/flotapponnier-openchainbench/api-mcp-mcp