Data Usdot
Server Details
US DOT Open Data (datahub.transportation.gov) Socrata MCP.
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
- 47.2% over 37 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-data-usdot
- GitHub Stars
- 0
- Server Listing
- data-usdot
TDQS
Scored across 34 tools
Most tools have distinct routing purposes, but there are genuine near-duplicates: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded all perform 'universal routing' (beta explicitly 'matches ask_pipeworx exactly'), and discover_tools vs suggest_questions both serve tool discovery. The long descriptions help differentiate within families, but an agent can still easily misselect among the router variants or the polymarket_* cluster.
Formatting is consistently snake_case, but verb conventions are mixed: many are verb_noun (resolve_entity, validate_claim, compare_entities, list_subscriptions) while core tools are bare nouns/verbs (datasets, metadata, query, remember, recall, forget). The ask_pipeworx_* family is predictable, but overall there is no single consistent pattern.
At 34 tools this is heavy even for a broad meta-aggregator, and several slots are redundant (the ask_pipeworx_beta variant that currently behaves identically, plus overlapping polymarket tools). Each tool may be defensible in isolation, but the count exceeds a well-scoped surface without clear justification for every entry.
Coverage is broad: the DOT Socrata surface has search (datasets), schema (metadata), and query, which is a complete read lifecycle for public open data. Memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list/recent_alerts), and verification flows are all present; only minor gaps like no bulk/multi-dataset query exist.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
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
Vermont Open Data (data.vermont.gov) Socrata MCP.
Virginia Open Data (datahub.va.gov) Socrata MCP.
Delaware Open Data (data.delaware.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.5 npm1MIT
- AlicenseNot gradedqualityAmaintenanceSearch and query government open-data portals (Socrata SODA API) via MCP.81 npm3Apache 2.0
- AlicenseNot gradedqualityCmaintenanceDataCambridge MCP — Cambridge open data (data.cambridgema.gov, Socrata SODA API).3 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for accessing Kansas City, MO open data through the Socrata SODA API. Enables querying and retrieving public datasets from data.kcmo.org.2 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.