Skip to main content
Glama

Chainlist

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Chainlist MCP — registry of EVM chains

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
47.1% over 37 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-chainlist
GitHub Stars
0
Server Listing
mcp-chainlist

TDQS

A4/5.0

Scored across 34 tools

Disambiguation3/5

Descriptions are exceptionally detailed and usually steer choice, but there are real overlaps: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded are three near-identical routers (beta is admitted to be a clone), and polymarket_arbitrage vs polymarket_edges vs bet_research all surface trade opportunities. entity_profile / recent_changes / resolve_entity / compare_entities also blur at the edges, though their descriptions disambiguate well enough.

Naming Consistency4/5

Nearly everything is snake_case, which is a strong baseline (list_chains, get_chain, resolve_entity, validate_claim, subscribe/unsubscribe). Minor deviations exist: bare verb pairs (remember/recall/forget), noun-prefix families (polymarket_*, pipeworx_*), and non-verb-led names (recent_alerts, deep_research), but the pattern stays predictable.

Tool Count3/5

34 tools is heavy and spans several unrelated domains (an EVM chain registry, a huge Pipeworx data gateway, and a Polymarket analytics suite), which makes the surface feel sprawling. The breadth of the gateway justifies many of them, but the count sits well above the comfortable 15-tool range and invites miscounts.

Completeness4/5

Core lifecycles are well covered: memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list_subscriptions/recent_alerts), entity resolution (resolve/compare/profile/changes/validate), and a deep Polymarket stack. Gaps are minor — the chain registry is read-only (reasonable), and there is no memory-update (only forget+remember), but no obvious dead ends for the stated gateway purpose.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources