OpenChainBench

io.github.Flotapponnierv1.0.0更新於 Oct 11, 2026

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

已驗證Streamable HTTP可網頁執行Data & AnalyticsFinance

概覽

AI 產生的概覽

讓助理列出、讀取並查詢 OpenChainBench 關於加密 RPC、跨鏈橋、預言機與交易平台的即時基準資料。

功能
OpenChainBench 是一個遠端 MCP 伺服器，提供已發布的加密基礎設施基準資料。其工具為 list_benchmarks、get_benchmark 與 query_prom，另有一個以 slug 存取的基準資源。資料涵蓋 RPC 延遲、聚合器、跨鏈橋、區塊鏈、預言機、價格來源、預測市場與永續合約 DEX，並附排名、方法論與新鮮度時間戳。
適用情境
當助理需要加密基礎設施服務供應商的最新、可引用效能數據或排名時使用，例如比較 RPC 或預言機延遲，或回答某個基準中哪家供應商領先的問題。
執行需求
需要一個遠端 MCP 用戶端，連線到 openchainbench.com 的 streamable HTTP 端點。未宣告任何身分驗證、API 金鑰、環境變數或標頭，也不需要本機套件或執行環境。
安裝前請注意
此伺服器為唯讀，不要求任何憑證。基準數值是第三方量測結果且會隨時間變動，依賴某個數字前請查看 freshness 或 asOf 欄位；草稿狀態的基準可能不顯示數字。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 OpenChainBench，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "openchainbench": {
      "type": "http",
      "url": "https://openchainbench.com/api/mcp/mcp"
    }
  }
}

README

OpenChainBench

Open, reproducible benchmarks for crypto infrastructure. Aggregators, bridges, RPCs, oracles, price feeds, prediction markets, perp DEXes, cross-chain messaging. Same metric, same conditions, every provider. Live at openchainbench.com.

[License: MIT] [Data: CC-BY-4.0] [Benchmarks] [MCP] [llms.txt]

OpenChainBench publishes one benchmark at a time, each shipping with the harness that produces its data. The goal is to make performance an observable property of crypto infra, measured in the open, by anyone who wants to add a provider or a metric.

Community-run, MIT-licensed harnesses + CC-BY-4.0 data, PRs from any party including the providers we benchmark.

At a glance

  • 94 live benchmark specs across 8 categories (RPCs, Trading, Aggregators, Bridges, Blockchains, RWA, Explorers, NFT APIs)
  • 50 self-contained Go harnesses, each shipping a /metrics Prometheus endpoint
  • 32 curated question/answer pages · 23 "alternatives to X" landing pages
  • 26 machine-readable API routes (citation, badges, MCP, feeds, per-format quotes)
  • One shared Prometheus, one materialization worker, CDN-fastpath snapshot store: cold reads in < 100 ms edge, no origin fan-out on hot paths

Quickstart

bash
pnpm installpnpm dev              # site at http://localhost:3000pnpm validate         # bench spec Zod schema check (run before opening a PR)pnpm typecheck        # tsc --noEmit

Adding a benchmark, writing a harness, or fixing a number: see CONTRIBUTING.md + the visual walkthrough at /contribute.

Machine-readable surfaces

Every benchmark is licensed CC-BY-4.0 and exposed through endpoints designed for citation by journalists, devs, and AI agents:

EndpointAudienceWhat it returns
/llms.txt · /llms-full.txtLLM crawlersPlain-text index (short) + full Markdown context (long) per the llmstxt.org convention.
/api/citableDevs, agentsFlat JSON: every benchmark with current value, leader, headline sentence, citation URL, OG image URL.
/api/stat/<slug>Devs, agentsSingle benchmark: full rankings, sparkline (24h), methodology, paste-ready quote, attribution URL.
/api/cite/<slug>/<format>Zotero, Mendeley, PerplexityCitation in bibtex, apa, ris, or txt with the correct MIME type.
/api/openapi.jsonLangChain, custom GPTs, generic clientsOpenAPI 3.1 schema describing every endpoint.
/api/mcp/mcpMCP clients (Claude Desktop, Cursor, ChatGPT tools)MCP server: list_benchmarks, get_benchmark, query_prom tools + openchainbench://benchmark/{slug} resource.
/api/freshnessLive UI, dashboards{slug → asOf ms} map. Edge-cached 5 s.
/api/llm-contextLLM system promptsEvery benchmark with rankings + methodology in one Markdown blob.
/benchmarks/<slug>/opengraph-imageX, LinkedIn, Slack, iMessage1200×630 PNG with current value + leader + sparkline. Auto-served on link unfurl.
/benchmarks/<slug>/share-card?template=...Manual export5 templates (ranking / snapshot / headline / compare / leaderboard), ?theme=dark supported.
/api/badge/<bench>/<provider>Provider sites, READMEs360×36 embeddable SVG with the provider's rank + headline figure.
/rss.xml · /feed.jsonFeed readers, agent toolingRSS 2.0 + JSON Feed 1.1 mirrors, one entry per live bench, updated on release.
/sitemap.xml · /robots.tsCrawlersEvery AI crawler (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, …) explicitly allowed.

Structured data on every bench page: Dataset + StatisticalReport + Observation + TechArticle + FAQPage + BreadcrumbList JSON-LD, plus a schema.org Dataset microdata graph layered on the visible "At a glance" infobox.

Journalist citation format (what /api/stat/<slug>.headlineSentence emits):

"Mobula leads head lag at 0.8s (p50, 24h) on Fastest onchain data provider.Source: OpenChainBench (https://openchainbench.com/benchmarks/aggregator-head-lag)"

Site surfaces

RouteWhat lives there
/Hero + Latest benchmarks table + Live dashboard
/benchmarks · /benchmarks/[slug]Catalog grid + per-bench leaderboard with chart, ledger, chain/region filters, share cards, FAQ
/benchmarks/[slug]/[chain]Chain-scoped bench view with per-chain explainer
/products/[slug]The one page per product: every bench it appears in, top-1 counts, related products, and a view per category it belongs to (Trading app, Perpetuals, Prediction markets, Data API, Bridge, RPC, Hyperliquid) selectable by pill or URL hash
/chains/[slug]Per-chain hub: live native price, TVL history, every bench that touches this chain grouped by category
/compare/[a]-vs-[b]Head-to-head comparison across shared benches, canonical alphabetical order enforced at the edge
/alternatives/[slug]"Alternatives to X" landing pages with live leaderboard from the referenced bench
/answers/[slug]Q&A pages backed by a live bench, formatted for AI answer engines
/hyperliquidHyperLiquid frontends cohort; each builder's dashboard (revenue, volume, first-active date) is the Hyperliquid view on its /products/[slug] page
/perps · /prediction-markets · /rpcVertical hubs aggregating multiple benches per topic
/mcpMCP server docs + install instructions
/methodology · /contribute · /team · /about · /press · /badgesStatic

Architecture

┌─────────────────────────┐    ┌───────────────────┐    ┌──────────────────────┐│  50 Go harnesses on     │    │  Shared Prometheus │    │ Materialization worker││  ocb-par-main (Paris)   │─── ▶│  (same VPS)        │───▶│ (same VPS, docker)   ││  each exposes /metrics  │    │  federates a few   │    │ sweeps every 60s     │└─────────────────────────┘    │  Railway regional  │    └──────┬───────────────┘                                │  harnesses         │           │                                └───────────────────┘           ▼                                                    ┌─────────────────────────┐                                                    │ Redis + CDN blob store   │                                                    │ (SRH at kv.opencha…)     │                                                    └──────────┬──────────────┘                                                               │                                                    ┌─────────────────────────┐                                                    │ Vercel Fluid Compute:    │                                                    │ pages read CDN blobs     │                                                    │ first, SRH as fallback,  │                                                    │ last-known-good on cold  │                                                    └─────────────────────────┘
  • Harnesses + Prometheus + worker + Redis + SRH run on one VPS (ocb-par-main in Paris) via docker compose. A handful of multi-region harnesses (rpc-capabilities-us/eu/sgp, evm-quote-latency, aggregator-head-lag regional) stay on Railway and federate into the VPS Prom.
  • Worker publishes atomic snapshots every 60 s to Redis + CDN blobs at kv.openchainbench.com/aggregate/{latest,benches/<slug>,variants/<slug>/<sig>}.json. Site reads CDN first (~20 ms edge), falls back to SRH, then to the last-known-good snapshot key on cold cache.
  • Site is Next.js 16 App Router on Vercel Fluid Compute. Auto-deploy from main on every push (with sitemap smoke test + auto-rollback + bench-page warm-up); dev branch runs on staging preview.
  • Middleware (src/middleware.ts) handles lowercase 308 normalization, /compare/<b>-vs-<a> → canonical alphabetical, 410 Gone for removed benches, 301 for renamed ones, and cache-key normalization on read-only public APIs.
  • Live stream relay (WebSocket at wss://stream.openchainbench.com/ws) is a separate service run by the OpenChainBench maintainers because it holds upstream API keys; the browser talks to it directly, Vercel only serves the static shell.

Full walkthrough with diagrams + a "clone-and-run-it-yourself" section is in docs/architecture.md.

Repo layout

benchmarks/        94 YAML specs, one per public benchmarkharnesses/         50 Go harnesses, each self-contained + Dockerizedanswers/           32 Q&A YAMLs backing /answers/<slug>alternatives/      23 "alternatives to X" YAMLs backing /alternatives/<slug>worker/            Materialization worker (sweeps Prom → publishes CDN + Redis blobs)infrastructure/    Shared Prometheus configsrc/               Next.js 16 site (App Router, ISR, Tailwind 4, TypeScript, Zod)docs/              architecture.md, methodology, walkthrough.mdscripts/           Spec validators + prebuild manifest generators.github/           CI: prod deploy, staging preview, sync dev from main

Contributing

Read CONTRIBUTING.md for the long-form guide. TL;DR:

  1. Float an idea in Discussions
  2. Open a 📊 Propose a benchmark issue with the metric + methodology
  3. Write the harness (Go recommended, any language shipping /metrics works)
  4. Host it (anywhere with HTTPS + public /metrics)
  5. Open a PR against dev: spec YAML + harness ref + Prom scrape config
  6. Review on the staging preview; merge to main when data lands

Editorial conventions

  • Same metric, same conditions. If two providers can't be measured identically, they don't share a bench.
  • Provider marketing does not shape published numbers. Public methodology + reproducible harness are the only source of truth.
  • Retirement over removal. Retired benches return 410 Gone with a link to the current catalog so previously-indexed URLs decay cleanly.
  • Freshness signals everywhere. Every citable surface carries dateModified + asOf so LLMs can tell fresh data from stale.
  • Draft benches never quote a number. If quorum drops, the page renders "awaiting samples" rather than a fabricated leader.

Community + license

License: harness code MIT · dataset CC-BY-4.0 · attribution required. See LICENSE.

來源：README.md，提交 6e26515

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v1.0.0最新Sep 16, 2026