io.github.Flotapponnier/openchainbench

Est-ce que io.github.Flotapponnier/openchainbench est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.Flotapponnier/openchainbench » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 6 outils

• compare_providers≈ 510 tokens

  Puts two or more named providers side by side on one benchmark, with each one's rank, measured value and success rate. Use when the user names the candidates themselves: "Alchemy or QuickNode?", "is Helius faster than Triton for Solana?", "compare Across and Stargate on fees". Find the benchmark slug with `search_benchmarks` first if you do not already have it. Providers the benchmark does not measure come back in `missing`: say they are not measured rather than implying they ranked badly. A provider measured but below the ranking floor comes back with rank null, which is also not a loss.

  Paramètres, retour & exemple (5)

  Paramètres

  • tier · string · optionnel
    Access cohort on chain RPC benchmarks: 'public' (default, free no-key endpoints) or 'keyed' (API-key providers such as Alchemy, QuickNode, Chainstack, GetBlock). Named providers usually live on the keyed cohort.
  • chain · string · optionnel
    Optional chain slice when the bench declares chains. Ignored on a bench that is already one chain, like solana-rpc.
  • region · string · optionnel
    Optional region slice when the bench declares regions.
  • benchmark · string · requis
    Benchmark slug, e.g. 'solana-rpc' or 'bridge-fee'. Get it from search_benchmarks.
  • providers · array · requis
    Two to ten provider names or slugs, as the user said them, e.g. ['Alchemy', 'QuickNode'].

  Exemple d'appel

  {"name": "compare_providers", "arguments": {"benchmark": "texte", "providers": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_benchmark≈ 684 tokens

  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. Chain RPC benchmarks (<chain>-rpc) rank two access cohorts apart: the free public endpoints (default) and the private, API-key providers (Alchemy, Chainstack, GetBlock, QuickNode). The default response carries both under `cohorts`; pass tier="keyed" to get the private cohort as the main record (rankings, quote, pageUrl). Never compare a public row with a private row: they are measured on different endpoints and cadences. 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" }) • User: "fastest Base RPC with an API key, Alchemy or QuickNode?" → get_benchmark({ slug: "base-rpc", tier: "keyed" }) Drafts return { error: "unknown_slug" }. Cite the returned `pageUrl` and use `quote` as the attribution line in your answer.

  Paramètres, retour & exemple (4)

  Paramètres

  • slug · string · requis
    Benchmark slug from list_benchmarks. e.g. 'aggregator-head-lag', 'bridge-quote-latency', 'l1-finality'.
  • tier · string · optionnel
    Optional access cohort on chain RPC benchmarks: 'public' (default, free no-key endpoints) or 'keyed' (private, API-key providers). Only honored when the bench declares tier dimensions.
  • chain · string · optionnel
    Optional chain filter, e.g. 'base', 'solana', 'bnb'. Only honored when the bench declares chain dimensions.
  • region · string · optionnel
    Optional region filter, e.g. 'us-east', 'eu-west', 'ap-southeast'. Only honored when the bench declares region dimensions.

  Exemple d'appel

  {"name": "get_benchmark", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_answers≈ 308 tokens

  Returns every published answer page: one plain question, the sentence that answers it from live data, and the benchmark the number comes from. Call this when the user asks a question in words rather than by benchmark name ("which bridge is cheapest for $300?", "which Solana RPC lands transactions fastest?"). Match the question, then call `get_benchmark` with the returned `benchmark` slug for the full ranking behind it. Returns one row per answer: { slug, question, answer, benchmark, chain?, url, benchmarkUrl } Cite `url` when the question itself is the claim, `benchmarkUrl` when the measurement is. Drafts are filtered out, and an answer whose benchmark has no defensible leader yet says so in `answer` rather than naming a winner.

  Paramètres, retour & exemple (1)

  Paramètres

  • benchmark · string · optionnel
    Optional benchmark slug filter: return only the answers built on that bench.

  Exemple d'appel

  {"name": "list_answers", "arguments": {"benchmark": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_benchmarks≈ 316 tokens

  A compact index of what OpenChainBench measures. One short row per benchmark: slug, title, category, the metric, the current value and who leads it. Use when the user asks what is measured at all ("what does OpenChainBench cover?", "do you track bridges?"). When they ask a question about a provider or a chain, use `search_benchmarks` instead: it ranks the catalogue against their words and costs far less to read. The catalogue holds over 200 benchmarks, so this is capped and filterable rather than exhaustive. Narrow with `category`, then open the one you need with `get_benchmark`. Categories: RPCs, Trading, Bridges, Blockchains, Aggregators, RWA, NFT APIs.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    How many rows to return, 1 to 50. Default 25.
  • category · string · optionnel
    Only this category: RPCs, Trading, Bridges, Blockchains, Aggregators, RWA or NFT APIs.

  Exemple d'appel

  {"name": "list_benchmarks", "arguments": {"limit": 1, "category": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• recommend_provider≈ 395 tokens

  Answers "which should I use for X" by picking the benchmarks that measure X and reporting who currently leads them. Pass the user's goal in their own words: "a Solana trading bot", "an indexer backfilling Base", "a wallet that needs price data", "bridging to Arbitrum". This returns measurements and the caveat that goes with them, not an endorsement. A leader on one benchmark is the leader of that one measurement over its stated window. Where the use case has a known caveat (a bot should read p99 rather than p50, an indexer is bound by archive depth) it comes back in `guidance`; pass it on, it is usually more useful than the ranking itself.

  Paramètres, retour & exemple (3)

  Paramètres

  • chain · string · optionnel
    Chain they are building on, e.g. 'solana', 'base', 'arbitrum'. Narrows the benchmarks considerably.
  • region · string · optionnel
    Optional region, e.g. 'eu-west', when latency from a location matters.
  • use_case · string · requis
    What the user is building or doing, in their words. e.g. 'solana trading bot', 'indexer', 'price feed for a wallet'.

  Exemple d'appel

  {"name": "recommend_provider", "arguments": {"use_case": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_benchmarks≈ 395 tokens

  Ranks the benchmark catalogue against a question in the user's own words and returns the best few matches. Use this when somebody asks which provider, chain or service is fastest, cheapest, most reliable or best for something. Pass their phrasing through: provider names, chain names and goals all match. • "which Solana RPC is fastest" -> search_benchmarks({ query: "solana rpc" }) • "Alchemy or QuickNode on Base?" -> search_benchmarks({ query: "alchemy quicknode base" }) • "cheapest way to bridge to Arbitrum" -> search_benchmarks({ query: "bridge arbitrum" }) Returns compact rows. Open the one you want with `get_benchmark` for the full ranking and a citation line. An empty result means nothing is measured for that question; say so rather than guessing.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    How many matches, 1 to 25. Default 8.
  • query · string · requis
    The user's question or keywords, verbatim. Provider and chain names work well.
  • category · string · optionnel
    Optional category filter: RPCs, Trading, Bridges, Blockchains, Aggregators, RWA, NFT APIs.

  Exemple d'appel

  {"name": "search_benchmarks", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://openchainbench.com/api/mcp/mcp