Data Colorado
Server Details
Colorado Information Marketplace — US government open data (data.colorado.gov) via the Socrata…
The last two health checks of this connector failed. 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
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-data-colorado
- GitHub Stars
- 0
- Server Listing
- mcp-data-colorado
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Many tools have well-articulated boundaries (company_facts vs entity_profile vs recent_changes, polymarket_fill_risk vs polymarket_edges), but there are real near-duplicates: ask_pipeworx / ask_pipeworx_beta (explicitly identical right now) / ask_pipeworx_grounded, deep_research vs discover_tools vs suggest_questions, and bet_research vs polymarket_arbitrage vs polymarket_edges all answer 'what should I bet on'. The sheer volume of marketing-style descriptions pushes the agent toward keyword matching rather than clean role separation.
All names are snake_case with no case-mixing, and the pack-prefixed families (polymarket_*, updown_*, ask_pipeworx*, pipeworx_*) are internally predictable. However, some tools are bare nouns with no verb (query, metadata, datasets, entity_profile, company_facts, deep_research) while others are verb_object, so the verb convention is not uniform across the set.
47 tools far exceeds what an agent can hold sensibly in one surface, and several of them exist only to route among the others (discover_tools, suggest_questions, ask_pipeworx x3, deep_research). The breadth is explainable as an aggregated gateway, but it is not scoped — a single server exposing Colorado Socrata datasets plus twelve prediction-market arbitrage tools is over-broad by any measure.
Lifecycle coverage is strong where it exists: memory has remember/recall/forget, subscriptions have subscribe/list/recent_alerts/unsubscribe, and the research/prediction-market domain is extremely deep. The notable gap is the namesake Colorado domain, which is read-only (datasets/metadata/query) with no catalog browsing, export, or cross-dataset join, and the entity/market surface has no update-style operations since it is inherently read-only.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Connecticut Open Data — US government open data (data.ct.gov) via the Socrata SoQL API: state…
Oregon Open Data — US government open data (data.oregon.gov) via the Socrata SoQL API: state…
Texas Open Data — US government open data (data.texas.gov) via the Socrata SoQL API: state…
Washington State Open Data — US government open data (data.wa.gov) via the Socrata SoQL API: state…
Related MCP Servers
- AlicenseNot gradedqualityBmaintenancedatos.gov.co — Colombia's national open-data portal (Socrata platform).163 npmMIT
- AlicenseNot gradedqualityCmaintenanceMono County GIS — Mono County & Mammoth Lakes, California open geospatial data (ArcGIS).90 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides access to 67 tools for querying Colorado legislative intelligence, including bills, statutes, rules, and campaign finance. It enables AI agents to analyze legislative attribution chains, stakeholder data, and legislator voting records.MIT
- AlicenseNot gradedqualityCmaintenanceOpen & historical US government bid solicitations from city/county portals — updated daily.87 npm2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.