Skip to main content
Glama

Server Details

U.S. Bureau of Transportation Statistics (BTS) — data.bts.gov open-data portal (Socrata platform).

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
46.8% over 38 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-bts
GitHub Stars
0
Server Listing
mcp-bts

TDQS

A3.9/5.0

Scored across 34 tools

Disambiguation3/5

The set has several overlapping families, especially ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research, and discovery/meta tools like discover_tools / suggest_questions / pipeworx_trending. Polymarket tools are mostly distinct, but bet_research, polymarket_edges, polymarket_arbitrage, and polymarket_edge_tracker share enough territory that selection can be ambiguous. The long descriptions mitigate many collisions, so it is not low, but boundaries are not clean enough for a 4 or 5.

Naming Consistency4/5

Nearly all names use snake_case, with clear prefixes for related tools such as ask_pipeworx_* and polymarket_*. There are minor deviations from strict verb_noun convention (entity_profile, dataset_columns, recent_alerts), but the overall pattern is predictable. It is mostly consistent with only small readability quirks.

Tool Count2/5

With 34 tools, the surface is heavy for a single MCP server even given the broad Pipeworx data-gateway scope. Several tools are redundant or experimental variants (ask_pipeworx_beta, multiple meta/onboarding tools), suggesting the set is over-expanded rather than tightly scoped. The count falls into the 25+ range that the rubric treats as too many.

Completeness4/5

The server covers a wide range of operations: data search/query, entity resolution, profiles, comparisons, change feeds, claim validation, memory, subscriptions, feedback, AI visibility, and prediction-market analytics. Core read/lifecycle operations are well represented, with only minor gaps such as no exact-name tool-schema lookup beyond discover_tools and no write operations for the BTS datasets. These gaps are workable rather than blocking.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous 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": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  },
        +  {
        +    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  }
        +]
      • changedInput schema / properties / market / description
        Previous 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 (\"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."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "topic": "fed"
        -  },
        -  {
        -    "topic": "btc"
        -  }
        -]New value: +[
        +  {
        +    "topic": "fed"
        +  },
        +  {
        +    "topic": "btc"
        +  },
        +  {
        +    "topic": "bitcoin"
        +  },
        +  {
        +    "topic": "fed rate decision"
        +  }
        +]
      • changedInput schema / properties / topic / description
        Previous 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

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.