Data Michigan
Server Details
Michigan Open Data (data.michigan.gov) Socrata MCP.
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-michigan
- GitHub Stars
- 0
- Server Listing
- data-michigan
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Several overlapping clusters make tool selection genuinely confusing: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools and suggest_questions all compete as entry points, and ask_pipeworx_beta explicitly duplicates the stable router. The 13 prediction-market tools overlap heavily (polymarket_edges vs polymarket_arbitrage vs polymarket_kalshi_spread vs bet_research), and ai_visibility_check vs scan_competitor_ai_presence is a wrapper/underlying pair. Descriptions are detailed and often direct callers, but the set-level boundaries remain fuzzy.
All names are snake_case, which keeps them readable, but there is no single verb_noun pattern: verb-led (list_subscriptions, validate_claim, resolve_entity), noun-only (datasets, metadata, query, entity_profile, company_facts), and mixed forms coexist. Prefixing is inconsistent too (ask_pipeworx_* vs pipeworx_feedback/pipeworx_trending vs discover_tools). Still parseable, not chaotic.
47 tools is heavy for any one server, and the surface is a grab bag of unrelated products: Michigan open-data query, SEC/entity research, prediction-market arbitrage, AI-visibility auditing, npm dependency scanning, memory, and subscriptions. Niche tools like kalshi_weather_edge, updown_divergence_rate, scan_dependency and generate_llms_txt earn their place only in a broad gateway, not a coherent 'Data Michigan' server. The count feels aggregated rather than scoped.
For Michigan open data, the read path is covered (search datasets, get schema, run SoQL) but there is no list-all/category browse, export/download, or geospatial operation, leaving notable gaps. Across the wider surface, memory and subscription lifecycles are mostly covered, but resolution_audit depends on polymarket_market / kalshi_market / polymarket_us_search tools that are not exposed, and subscriptions lack an update operation. Workable but with real dead ends.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Pennsylvania Open Data (data.pa.gov) Socrata MCP.
Vermont Open Data (data.vermont.gov) Socrata MCP.
Virginia Open Data (datahub.va.gov) Socrata MCP.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for accessing data.ny.gov datasets via the Socrata Open Data API, enabling search, query, metadata retrieval, and column value exploration.81 npm1MIT
- AlicenseNot gradedqualityBmaintenanceSearch and query government open-data portals (Socrata SODA API) via MCP.592 npm4Apache 2.0
- AlicenseNot gradedqualityBmaintenanceDataCambridge MCP — Cambridge open data (data.cambridgema.gov, Socrata SODA API).157 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for querying City of Novi, Michigan open geospatial data (ArcGIS), enabling dataset search, layer querying, and schema inspection.88 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.