Data Vermont
Server Details
Vermont Open Data (data.vermont.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-vermont
- GitHub Stars
- 0
- Server Listing
- MCP Data Vermont
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Several families have genuinely unclear boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded and deep_research all claim to be the routing entry point, and the beta tool openly states it is byte-identical to the stable one. Likewise polymarket_edges, polymarket_arbitrage and bet_research all scan Polymarket for mispricing, and entity_profile / company_facts / compare_entities / recent_changes overlap on company research. Descriptions are unusually verbose and do a lot of triage work, but the agent still has to read paragraphs to pick correctly.
Casing is uniformly snake_case, which helps, but the verb/noun convention is mixed: verb_noun (ask_pipeworx, resolve_entity, validate_claim, scan_dependency) sits beside bare nouns and bare verbs (entity_profile, company_facts, datasets, metadata, query, remember, forget). Readable overall, but the naming does not encode the tool's action type.
47 tools is far past the point of comfortable scoping, especially for a server whose name and three of its tools describe a Vermont open-data catalog. The remaining ~44 tools are an unrelated general-purpose data gateway (SEC, FDA, Polymarket, Kalshi, subscriptions, memory), so the count is not justified by the apparent scope.
The Vermont legs (datasets, metadata, query) form a coherent read-only catalog surface with no obvious missing operation. However, the broader catalog has dead ends: descriptions repeatedly reference tools that are not in this set (fetch_url, polymarket_market, kalshi_market, polymarket_us_search, deps.dev:version), so agents will hit references they cannot resolve.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Virginia Open Data (datahub.va.gov) Socrata MCP.
Pennsylvania Open Data (data.pa.gov) Socrata MCP.
Michigan Open Data (data.michigan.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 gradedqualityBmaintenanceDataCambridge MCP — Cambridge open data (data.cambridgema.gov, Socrata SODA API).157 npmMIT
- AlicenseNot gradedqualityBmaintenanceSearch and query government open-data portals (Socrata SODA API) via MCP.150 npm4Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server for accessing Kansas City, MO open data through the Socrata SODA API. Enables querying and retrieving public datasets from data.kcmo.org.99 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.