Skip to main content
Glama

Fmcsa

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

US motor-carrier registry: DOT/MC/name lookup, operating authority, safety — keyless

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
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-fmcsa
GitHub Stars
0
Server Listing
mcp-fmcsa

TDQS

A4.1/5.0

Scored across 35 tools

Disambiguation3/5

Several tools overlap heavily: ask_pipeworx, ask_pipeworx_beta (currently identical to the stable router), ask_pipeworx_grounded, and deep_research all route natural-language questions, differing only in tier/grounding semantics. discover_tools vs suggest_questions, and entity_profile vs compare_entities vs recent_changes vs resolve_entity, also require careful reading to separate. The descriptions do disambiguate on close inspection, but the set forces agents to parse long text before picking.

Naming Consistency4/5

Names are uniformly snake_case with sensible namespace prefixes (fmcsa_, polymarket_, pipeworx_), and the memory/subscription trios (remember/recall/forget, subscribe/unsubscribe/list_subscriptions) are predictable. Minor inconsistency in verb-vs-noun ordering: some are verb_noun (compare_entities, resolve_entity, validate_claim) while others are noun-first (entity_profile, recent_alerts, recent_changes).

Tool Count3/5

At 35 tools this is on the heavy side, and a few seem redundant (ask_pipeworx_beta duplicating ask_pipeworx, four overlapping answer/routing tools, two discovery tools). The very broad universal-data-gateway scope justifies much of the count, but pruning the redundant variants would tighten the set.

Completeness4/5

The surface is broad: discovery (discover_tools, suggest_questions), identity resolution, entity profiling, comparison, research, claim validation, memory, subscriptions, feedback, and domain suites (FMCSA, Polymarket). Minor gaps exist, such as no memory update (only remember/forget/recall) and no explicit bulk retrieval of raw tool schemas beyond discover_tools. Core lifecycle operations for the major flows are present.

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": "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"
+  }
+]
      • changedInput schema / properties / market / description
        Previous 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."
    • Changedpolymarket_kalshi_spread1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
  2. 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": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]
      • 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 (\"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."
    • Changedpolymarket_kalshi_spread1 field changed
      • 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

  • nexusfeed-mcp

    NexusFeed
    A
    license
    A
    quality
    C
    maintenance
    Real-time LTL freight fuel surcharge rates for 9 US carriers and US state ABC liquor license compliance lookups (CA, TX, NY, FL). Every response includes a verifiability block with extraction confidence and source URL so agents can assess data quality before acting.
    6
    40 PyPI
    1
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources