Regulatory & Compliance Intelligence MCP
REMOTE · COMPLIANCE-MCP-PRODUCTION.UP.RAILWAY.APP
Regulatory compliance, FDA recalls, federal register, enforcement actions & comment deadlines.
Available components
Last scanned (59 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 29 Jul 2026.
Category News and Social
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Aug 26 0
- HSTS header: unverified → fail ▼ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Aug 2026 · Probed https://compliance-mcp-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of compliance-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 502 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://compliance-mcp-production.up.railway.app/mcp | HTTP error | 502 | |
| http (plaintext) | http://compliance-mcp-production.up.railway.app/mcp | HTTPS enforced | 301 | https://compliance-mcp-production.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
brief_summary ~165
Get the top 5 signals from today's brief as structured JSON — a cheap sample of the full daily_brief. Returns the day's highest-priority items (no prose) so an agent can decide whether to buy the full brief. PAID: $0.50 (vs the full daily_brief price). Defaults to today (UTC). On a 402, settle the returned payment challenge and re-call with the SAME args plus payment_tx=<reference>. An Authorization: Bearer fnet_ key bypasses payment.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| date | – | – | brief date YYYY-MM-DD (default today, UTC). |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
Structured output declared, but exposes no named fields.
No examples provided.
comment_deadlines ~162
Track upcoming public-comment deadlines for proposed rules from the Federal Register — what regulatory compliance and regulatory-affairs agents monitor constantly. Sorted by soonest deadline. PAID: $0.01 per query after the daily free allowance (25/day). On a 402, settle the returned payment challenge and re-call with the SAME args plus payment_tx=<reference>. An Authorization: Bearer fnet_ key bypasses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| days_ahead | – | – | look-ahead window in days (1-365, default 30). |
| industry | – | – | optional industry filter. |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
Structured output declared, but exposes no named fields.
No examples provided.
compliance_alerts ~188
Monitor active compliance alerts for an industry — action_required and critical items from the Federal Register, openFDA, and CPSC, sorted by deadline urgency for ongoing compliance monitoring. The premium tool: "what do I need to worry about in pharma this week?" PAID: $0.01 per query after the daily free allowance (25/day). On a 402, settle the returned payment challenge and re-call with the SAME args plus payment_tx=<reference>. An Authorization: Bearer fnet_ key bypasses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| industry | string | yes | e.g. "pharma", "finance", "food". |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
| severity | – | – | optional filter (else action_required + critical). |
Structured output declared, but exposes no named fields.
No examples provided.
daily_brief ~248
Get the curated daily compliance brief — the day's most significant regulatory developments in one package: new final rules (Federal Register), open comment deadlines closing within 14 days, fresh recalls (openFDA & CPSC), and enforcement actions above $50K. Each brief carries a cryptographic provenance attestation so a buyer can verify it was produced by this server, unaltered. PAID: $10 per brief. Defaults to today (UTC); a brief expires at the next midnight UTC. On a 402, settle the returned payment challenge and re-call with the SAME args plus payment_tx=<reference>. An Authorization: Bearer fnet_ key bypasses payment.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| date | – | – | brief date YYYY-MM-DD (default today, UTC). |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
| stripe_token | – | – | Stripe Checkout Session id (cs_…), when re-calling after paying the Stripe payment link (alternative to x402). Can also be supplied via the X-Stripe-Token header. |
Structured output declared, but exposes no named fields.
No examples provided.
daily_digest ~162
Monitor a structured daily regulatory digest — new rules, recalls, enforcement, and comment deadlines from the Federal Register, openFDA, and CPSC over the last ~2 days, organized by severity and type for compliance monitoring. PAID: $0.02 per query after the daily free allowance (25/day). On a 402, settle the returned payment challenge and re-call with the SAME args plus payment_tx=<reference>. An Authorization: Bearer fnet_ key bypasses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| industry | – | – | optional industry filter. |
| jurisdiction | – | – | federal | state | eu. |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
Structured output declared, but exposes no named fields.
No examples provided.
enforcement_actions ~178
Track regulatory enforcement actions (incl. OSHA citations and SEC enforcement) from the Federal Register, with parsed penalty amounts and context, filterable by agency, company, industry, or minimum penalty. PAID: $0.01 per query after the daily free allowance (25/day). On a 402, settle the returned payment challenge and re-call with the SAME args plus payment_tx=<reference>. An Authorization: Bearer fnet_ key bypasses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | – | – | enforcing agency, partial match. |
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| company | – | – | company name, partial match. |
| industry | – | – | industry tag filter. |
| min_penalty | – | – | minimum penalty amount (USD). |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
Structured output declared, but exposes no named fields.
No examples provided.
mint_info ~65
Get FoundryNet Data Network info for compliance monitoring agents. FREE. Returns how to attest your agent's compliance/regulatory analysis for verifiable provenance, plus the sister data servers (gov-contracts, brand-intel, patent-intel, financial-signals, weather-intel).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
recall_check ~183
Check product and FDA recalls from openFDA (food/drug/device) and CPSC (consumer products), with affected products and severity (Class I / injuries → critical). PAID: $0.01 per query after the daily free allowance (25/day). On a 402, settle the returned payment challenge and re-call with the SAME args plus payment_tx=<reference>. An Authorization: Bearer fnet_ key bypasses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| category | – | – | category keyword (food, toy, drug, etc.). |
| company | – | – | recalling firm / manufacturer, partial match. |
| days_back | – | – | only recalls in the last N days. |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
| product | – | – | product name/keyword. |
Structured output declared, but exposes no named fields.
No examples provided.
search_regulations ~268
Search regulatory updates and final rules from the Federal Register, openFDA, and CPSC by industry, agency, type, keyword, or severity — regulatory compliance and compliance monitoring intelligence, newest first. PAID: $0.01 per query after a daily free allowance (25/day). On a 402, settle the returned payment challenge and re-call with the SAME args plus payment_tx=<reference>. agent_id scopes your allowance; an Authorization: Bearer fnet_ key bypasses it.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | – | – | issuing agency, partial match. |
| agent_id | – | – | stable id for your agent (scopes the free-tier counter). |
| days_back | – | – | only entries published in the last N days. |
| industry | – | – | one of healthcare, pharma, finance, manufacturing, food, consumer_products, energy, technology, construction, transportation, agriculture, defense. |
| keyword | – | – | free-text over title + summary. |
| limit | integer | – | max rows (1-200, default 50). |
| payment_tx | – | – | payment transaction reference, when re-calling after a 402. |
| regulation_type | – | – | final_rule|proposed_rule|notice|recall|enforcement|guidance|alert. |
| severity | – | – | info|warning|action_required|critical. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Regulatory & Compliance Intelligence MCP server?
Regulatory & Compliance Intelligence MCP is a hosted endpoint at https://compliance-mcp-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · compliance-mcp-production.up.railway.app
claude mcp add --transport http foundrynet-compliance-mcp 'https://compliance-mcp-production.up.railway.app/mcp'
What is the Regulatory & Compliance Intelligence MCP server?
Regulatory & Compliance Intelligence MCP is listed in the public MCP registry as io.github.FoundryNet/compliance-mcp. Regulatory compliance, FDA recalls, federal register, enforcement actions & comment deadlines. This page covers its hosted endpoint (https://compliance-mcp-production.up.railway.app/mcp).
Is the Regulatory & Compliance Intelligence MCP server safe to use?
Regulatory & Compliance Intelligence MCP scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Regulatory & Compliance Intelligence MCP server expose?
Regulatory & Compliance Intelligence MCP exposes 9 tools: search_regulations, compliance_alerts, recall_check, enforcement_actions, comment_deadlines, and 4 more. Their descriptions and schemas cost roughly 1,619 tokens of context every time the server is loaded.
Does the Regulatory & Compliance Intelligence MCP server require authentication?
No. We connected to Regulatory & Compliance Intelligence MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Regulatory & Compliance Intelligence MCP server still maintained?
Regulatory & Compliance Intelligence MCP has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 29 July 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.