Skip to main content
Glama

Data Austin

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

DataAustin MCP — Austin, TX open data (data.austintexas.gov, Socrata SODA API).

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

TDQS

A3.9/5.0

Scored across 34 tools

Disambiguation3/5

The extremely detailed descriptions do heavy lifting to route callers (PREFER OVER, START HERE, USE THIS when), which prevents most confusion. However, real overlap exists: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded are three variants of the same router (beta explicitly states it is currently identical to base), and the polymarket cluster (arbitrage/edges/edge_tracker/bet_research) plus discover_tools vs suggest_questions all cover adjacent ground.

Naming Consistency4/5

Nearly all names are snake_case with consistent prefixes (polymarket_*, austin_*, ask_pipeworx_*), and the memory and subscription groups are clean. The only wrinkle is a mix of verb_noun (scan_dependency, validate_claim, generate_llms_txt) and noun-phrase (entity_profile, recent_changes, ai_visibility_check) constructions, but nothing is chaotic.

Tool Count2/5

At 34 tools this exceeds the comfortable 3-15 band and crosses into 'heavy.' Several tools are redundant variants (three ask_pipeworx routers, five polymarket tools) that inflate the count rather than each earning a distinct place.

Completeness4/5

For a broad data-gateway mission the surface is fairly complete: memory has a full remember/recall/forget triad, subscriptions have create/list/fire-read/delete, entity resolution and comparison are covered, and Polymarket has scan/arb/tracker/fill/spread. Only minor gaps (e.g. no write path or dataset metadata beyond the three Austin tools) keep it below full marks.

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
    B
    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.
    247 npm
    MIT

  • mcp-data-ny

    pipeworx-io
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for accessing data.ny.gov datasets via the Socrata Open Data API, enabling search, query, metadata retrieval, and column value exploration.
    147 npm
    1
    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