Skip to main content

Regulatory & Compliance Intelligence MCP

by io.github.FoundryNet

Server Details

Regulatory compliance, FDA recalls, federal register, enforcement actions & comment deadlines.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Unhealthy
Last Tested: 2026-09-06 18:20
Transport: Streamable HTTP
URL
Repository: FoundryNet/compliance-mcp
GitHub Stars: 0
Server Listing: compliance-mcp

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

8 tool updatesJul 16, 2026

Changedbrief_summary1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

Changedcomment_deadlines1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

Changedcompliance_alerts1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

Changeddaily_brief1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

Changeddaily_digest1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

Changedenforcement_actions1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

Changedrecall_check1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

Changedsearch_regulations1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

1 tool updateJun 22, 2026
- Addedbrief_summary

1 tool updateJun 21, 2026

Changeddaily_brief1 field changed

addedInput schema / properties / stripe_token

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Stripe Checkout Session id (cs_…), when re-calling after\npaying the Stripe payment link (alternative to x402). Can also be\nsupplied via the X-Stripe-Token header."
+}

1 tool updateJun 19, 2026
- Addeddaily_brief
7 tool updatesJun 18, 2026
- First observedcomment_deadlines
- First observedcompliance_alerts
- First observeddaily_digest
- First observedenforcement_actions
- First observedmint_info
- First observedrecall_check
- First observedsearch_regulations

Frequently Asked Questions

Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.

Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
- GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
- DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.

The HTTP ownership file has this structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "claim": "glama_claim_..."
}

Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.

If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.

For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.

Discussions

No comments yet. Be the first to start the discussion!

Login with GitHub to comment

Related MCP Connectors

FDA Approvals A
io.github.guptaprakhariitr
FDA drug approvals, 510(k) device clearances, recalls and adverse-event reports.
Government Data Biology & Medicine Open Data
421
Regulatory Monitor
io.github.martc03
Federal Register monitoring and regulations.gov tracking. 4 MCP tools for regulatory compliance.
Government Data Legal & Compliance Monitoring
25
FDA Recall Alerts — Food & Product Safety (fdarecall)B
com.a2awire
FDA food, drug and device recalls: Class I alerts, firms, status. Updated weekly.
Government Data Open Data Health & Wellness
161
premium-data-mcp-server A
com.thenextgennexus
Federal contracts, FDA recalls, business registrations, Amazon products — B2B intel.
Government Data E-commerce & Retail
52

Related MCP Servers

Healthcare Compliance MCP
Biology & Medicine Research & Data Legal & Compliance
red-cars-io
F
license
Not graded
quality
D
maintenance
Enables AI agents to access FDA and ClinicalTrials.gov data for medical device compliance, adverse event monitoring, and regulatory due diligence.
Updated 4 months ago (2026-05-05 01:38 UTC)
-
EMA MCP Server
Biology & Medicine Government Data Research & Data
openpharma-org
A
license
A
quality
D
maintenance
Provides access to European Medicines Agency regulatory data including EU drug approvals, safety reviews, orphan designations, supply shortages, and comprehensive pharmaceutical documentation for regulatory intelligence.
Updated 7 months ago (2026-01-27 20:35 UTC)
1
3
MIT
Constat — 483 Risk Radar
Biology & Medicine Government Data Research & Data
thehealthai
A
license
A
quality
A
maintenance
The MCP server behind Constat — FDA & NHTSA regulatory-risk intelligence for AI agents, over the Model Context Protocol. Live public regulatory data — recalls, adverse events, warning letters, 510(k) premarket evidence, postmarket drift signals, reimbursement pathways, and vehicle safety. Decision support, not regulatory advice.
Updated 23 days ago (2026-08-14 23:02 UTC)
14
MIT
Obsidian Regulatory MCP
Legal & Compliance Research & Data Search
richbile
A
license
Not graded
quality
B
maintenance
Provides AI assistants with verified regulatory data from 850+ official sources across 50+ jurisdictions, enabling accurate compliance research.
Updated 3 months ago (2026-06-18 08:51 UTC)
MIT

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation2/5

Several tools provide overlapping aggregated regulatory summaries: daily_brief, daily_digest, compliance_alerts, and brief_summary all cover similar content (rules, recalls, enforcement, deadlines) with only subtle differences in curation, price, and time window. An agent could easily misselect between them.

Naming Consistency4/5

All tool names are lowercase snake_case with two words, mostly noun phrases (e.g., comment_deadlines, recall_check). The only deviation is search_regulations which is verb-led, but the pattern is consistent and predictable.

Tool Count5/5

9 tools is appropriate for a regulatory intelligence server; each tool addresses a distinct type of query (search, alerts, deadlines, enforcement, recalls, daily summaries) without bloat.

Completeness4/5

The surface covers core regulatory monitoring needs: searching updates, tracking deadlines, enforcement, recalls, and daily digests. Minor gaps such as a dedicated get_regulation_by_id tool or historical trend analysis are not critical for the stated purpose.

Resources