Skip to main content
Glama

Server Details

FAA Regulations MCP — US Federal Aviation Regulations (14 CFR, 'FARs').

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
42.9% over 38 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-faa-regulations
GitHub Stars
0
Server Listing
FAA Regulations MCP

TDQS

A3.8/5.0

Scored across 33 tools

Disambiguation2/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all act as routers (beta is explicitly 'identical' to ask_pipeworx), and polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, and polymarket_edge_tracker blur together for betting analysis. Entity tools (entity_profile, recent_changes, resolve_entity, compare_entities) also overlap enough to invite misselection.

Naming Consistency3/5

Names are all snake_case but mix verb_noun (compare_entities, resolve_entity, validate_claim) with noun_verb/noun_noun patterns (entity_profile, faa_regulation, recent_alerts, polymarket_edges). The convention is readable but not uniform.

Tool Count2/5

33 tools is heavy for any server, and drastically mismatched for a server named 'Faa Regulations' where only faa_regulation and faa_search are domain-relevant. The remaining 31 are generic Pipeworx aggregator/meta tools that inflate the surface.

Completeness3/5

For FAA regulations, the surface covers reading a regulation, keyword search, and listing a part's sections, which handles core lookup needs. However, it lacks amendment/effective-date history, cross-references, and change monitoring, and the rest of the tool set is unrelated to the FAA domain.

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

  • A
    license
    A
    quality
    A
    maintenance
    Legacy eCFR MCP listing for reading CFR text, FAR, DFARS, and agency supplements. Maintenance transferred to AcqAgent: https://github.com/acqagent/mcps. This listing's build and 13-tool evaluation cover eCFR only, not the other servers in the 1102tools monorepo.
    13
    24
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Search and trace US federal rules across the Federal Register (proposed/final rules and notices), the eCFR (codified, point-in-time CFR full text, locally mirrored), and Regulations.gov (rulemaking dockets and public comments) via MCP.
    98 npm
    1
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    An MCP server that turns the US Code of Federal Regulations into an agent-navigable citation graph, enabling traversal of regulatory references and detection of stale citations via structured tools.
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.