Skip to main content
Glama

Data Mo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Missouri Open Data (data.mo.gov) Socrata MCP.

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
48.6% over 37 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-data-mo
GitHub Stars
0
Server Listing
mcp-data-mo

TDQS

A4/5.0

Scored across 34 tools

Disambiguation3/5

The flooding of router-style meta-tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) overlaps heavily, and ask_pipeworx_beta is explicitly 'currently matches ask_pipeworx exactly,' creating a genuine selection hazard. The Polymarket family (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) also overlaps, though the descriptions work hard to delineate angles. Distinctions exist but the set is large enough that misselection is plausible.

Naming Consistency4/5

Nearly all names use a predictable snake_case convention (ask_pipeworx, compare_entities, resolve_entity, entity_profile, polymarket_edges), which reads cleanly. The only inconsistency is mixing verb-first (validate_claim, discover_tools) with noun-first (datasets, metadata, query) patterns, but nothing is chaotic or camelCase-mixed.

Tool Count3/5

At 34 tools this is well above the comfortable 3-15 band, and the breadth (SEC/FDA/FRED routing, Polymarket, Missouri Open Data, memory, subscriptions, AI-visibility) partly justifies the volume. However, the beta router duplicate and multiple closely-related Polymarket tools suggest some tools don't independently earn their place. Borderline-heavy rather than clearly justified.

Completeness4/5

Coverage is broad and mostly closed-loop: memory has full remember/recall/forget, subscriptions have create/list/cancel plus a feed, Missouri data has search/metadata/query, and Polymarket gets deep lifecycle treatment (research, edges, arb, fill risk, cross-venue, tracking). Minor gaps remain (e.g. no explicit record read/regeneration tooling beyond search_within), but agents can work around them.

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": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]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 (\"when-will-bitcoin-hit-150k\"), 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."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_spread1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
  2. 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": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]
      • 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 (\"when-will-bitcoin-hit-150k\"), 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_spread1 field changed
      • 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

  • mcp-data-kcmo

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for accessing Kansas City, MO open data through the Socrata SODA API. Enables querying and retrieving public datasets from data.kcmo.org.
    2 npm
    MIT

  • mcp-data-ny

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for accessing data.ny.gov datasets via the Socrata Open Data API, enabling search, query, metadata retrieval, and column value exploration.
    5 npm
    1
    MIT

  • data-santaclara

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for querying Santa Clara County open data via Socrata APIs, enabling dataset search, SoQL queries, and metadata retrieval.
    3 npm
    MIT
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