Data Denver
Server Details
DataDenver MCP — Denver open data (opendata-geospatialdenver.hub.arcgis.com, ArcGIS REST 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
- 45.8% over 38 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-data-denver
- GitHub Stars
- 0
- Server Listing
- data-denver
TDQS
Scored across 39 tools
Several tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and discover_tools all route questions to the same 6,032-tool catalog, and bet_research/polymarket_edges/polymarket_arbitrage/polymarket_edge_tracker/polymarket_fill_risk/polymarket_kalshi_spread all target prediction-market opportunities with different angles. The descriptions are detailed enough to distinguish them, but an agent could easily pick the wrong one.
Most tools use lowercase snake_case with verb_noun patterns (ask_pipeworx, denver_query, resolve_entity, validate_claim), but there are deviations: ai_visibility_check and scan_competitor_ai_presence use different verb styles, and the polymarket_* family mixes nouns and verbs inconsistently (polymarket_edges vs polymarket_fill_risk vs polymarket_kalshi_spread). The pipeworx_* prefix is used for some meta-tools but not others.
39 tools is heavy for a single server, and many are meta-tools that wrap the same underlying catalog (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions). The prediction-market cluster alone accounts for 7 tools. While each has a distinct function, the set feels bloated and would be better split into separate servers.
The server covers its apparent domains well: data lookup, entity research, prediction markets, memory, subscriptions, and feedback all have lifecycle coverage. Minor gaps exist (e.g., no direct tool for updating a saved memory beyond forget/remember/recall, and the AI-visibility tools lack a delete/update), but the core workflows are complete.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
5 tool updates
- Added
company_facts - Added
kalshi_weather_edge - Added
release_calendar_markets - Added
resolution_audit - Added
resolution_diff
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious 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" + } +] - changed
Input schema / properties / market / descriptionPrevious 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."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious 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" + } +] - changed
Input schema / properties / market / descriptionPrevious 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."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious 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
DataBaltimore MCP — Baltimore open data (data.baltimorecity.gov, ArcGIS REST API).
DataDC MCP — Washington, DC open data (opendata.dc.gov, ArcGIS REST API).
DataDetroit MCP — Detroit open data (data.detroitmi.gov, ArcGIS REST API).
DataNashville MCP — Nashville open data (data.nashville.gov, ArcGIS REST API).
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceDataCambridge MCP — Cambridge open data (data.cambridgema.gov, Socrata SODA API).3 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables querying Washington DC open data from opendata.dc.gov and ArcGIS REST API through MCP.2 npmMIT
- AlicenseNot gradedqualityCmaintenanceThis MCP server provides access to City of Houston GIS open geospatial data, enabling search, query, and schema retrieval of datasets like parcels and zoning through ArcGIS feature services.3 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables searching and querying City of Pittsburgh GIS open geospatial data (parcels, zoning, public works) through ArcGIS feature services via MCP tools.4 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.