FCC Regulations MCP — US Federal Communications Commission rules (47 CFR).
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.
Scored across 33 tools
Descriptions are unusually explicit about routing and 'PREFER OVER' rules, which sharply separates most tools (e.g. fcc_regulation vs fcc_regulations_search, entity_profile vs recent_changes vs compare_entities). However, ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research form a cluster where boundaries (default vs grounded vs beta vs multi-source) require careful reading, and six polymarket_* tools plus bet_research overlap enough that misselection is plausible.
Everything is uniformly snake_case, which is a strong baseline. But the semantic pattern is mixed: some are verb_noun (list_subscriptions, resolve_entity, validate_claim), some are bare/peripheral verbs (remember/recall/forget), and many are product-prefixed (pipeworx_*, polish fcc_*, polymarket_*), so the conventions shift across sub-domains.
33 tools is heavy, and the server is titled 'Fcc Regulations' yet only two tools (fcc_regulation, fcc_regulations_search) serve that domain — the rest are unrelated meta-tools, prediction-market tools, memory, and subscription management. The count is grossly mismatched to the apparent stated purpose, even if each individual tool has a defensible scope.
For the FCC rules domain, get-by-citation plus keyword search covers reading the full 47 CFR surface, and the descriptions point to sibling packs for filings/licensing (ULS, ECFS, broadband maps). Minor gaps exist (no tool for FCC enforcement/rulemaking updates or license data within this set), but the core read workflow is covered.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bet_research2 fields changedInput 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"
+ }
+]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."bet_research2 fields changedInput 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"
+ }
+]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."polymarket_kalshi_spread2 fields changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]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."EPA Regulations MCP — US Environmental Protection Agency regulations (40 CFR).
SEC Regulations MCP — US securities regulations (17 CFR).
FDA Regulations MCP — US Food & Drug Administration regulations (21 CFR).
FAA Regulations MCP — US Federal Aviation Regulations (14 CFR, 'FARs').
Add one secure layer between your agents and this server.