Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Fda Regulations

NPM · @PIPEWORX/MCP-FDA-REGULATIONS · 2 COMPONENTS

FDA Regulations MCP — US Food & Drug Administration regulations (21 CFR).

+3 this week 81 Trust /100

Last scanned (9 hours ago)

Scores higher than 69% of npm servers

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-fda-regulations). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 706 tokens (~353/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Security disclosure: unverified → fail ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Stability: unverified → 0.10 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 29 Oct 26 78

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-fda-regulations@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-fda-regulations
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-fda-regulations/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3635939349
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:a356cd832d2a31e496917d39149a7ce1e156a2abed80959ab7f9275b4510d1fa78c3fa2bd144b335df8c4c1a1a4616fef1f6f0721b3211c730456cdc7

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~650 tokens

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 →

Tool Tokens
fda_regulation ~403

Get the full text of one FDA regulation — a US Food & Drug Administration rule codified in 21 CFR — by its citation. Returns the exact regulatory wording currently in force. Answers "what does 21 CFR 211 require", "what is the FDA regulation for X", "does the FDA require X", "read 21 CFR 211.100", "the FDA good manufacturing practice rule". Forgiving citation input: "211.100", "21 CFR 211.100", "§211.100", even "211.100(a)" (paragraph stripped to the section). Covers 21 CFR part 211 current good manufacturing practice (cGMP / GMP) for finished drugs, part 210 cGMP general, part 820 quality system regulation / QMSR for medical devices, part 801 medical device labeling, part 101 food labeling / nutrition facts, part 314 new drug applications (NDA/ANDA), part 807 device establishment registration, part 111 dietary supplement cGMP, part 1308 controlled substance schedules — the whole of Title 21 (food, drugs, devices, cosmetics, biologics). This is FDA REGULATIONS (the rules/regulatory text); for FDA DATA (drug labels, adverse events, recalls) use the openfda tools. Pass a whole part (e.g. "211" or "820") to get that part's section list. Example: fda_regulation({ citation: "211.100" }) -> written procedures / process control; fda_regulation({ citation: "21 CFR 101.9" }) -> nutrition labeling. Keyless.

NameTypeReqDescription
citationstringyesFDA regulation citation. A section: "211.100", "21 CFR 211.100", "§820.35", "211.100(a)". Or a whole part: "211", "part 820" -> returns the part's section list.

No output schema declared.

No examples provided.

fda_search ~247

Keyword search across FDA regulations — US Food & Drug Administration rules in 21 CFR. Answers "what FDA regulations cover X", "the FDA regulation / rule about X", "find the FDA requirement for X". Great for topics: good manufacturing practice (GMP / cGMP), quality system regulation, medical device labeling, drug labeling, nutrition facts / food labeling, new drug applications, dietary supplements, cosmetics, biologics, controlled substances, current good manufacturing practice for drugs and devices. Returns matching FDA regulations with citation (21 CFR), heading, excerpt, and source URL. This searches FDA REGULATIONS (regulatory text); for FDA DATA (drug labels, adverse events, recalls) use the openfda tools. Example: fda_search({ query: "medical device labeling" }); fda_search({ query: "good manufacturing practice", limit: 15 }). Keyless.

NameTypeReqDescription
limitnumber–Max results to return, 1-20 (default 10).
querystringyesFDA-regulation topic or phrase, e.g. "medical device labeling", "good manufacturing practice", "nutrition labeling", "quality system", "new drug application".

No output schema declared.

No examples provided.

Install

How do I install the Fda Regulations MCP server?

Fda Regulations runs locally as an npm package, launched with npx -y @pipeworx/mcp-fda-regulations. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-fda-regulations

# add to Claude Code
claude mcp add pipeworx-io-fda-regulations -- npx -y @pipeworx/mcp-fda-regulations
Common questions

What is the Fda Regulations MCP server?

Fda Regulations is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fda-regulations. FDA Regulations MCP, US Food & Drug Administration regulations (21 CFR). This page covers its npm package (@pipeworx/mcp-fda-regulations).

Is the Fda Regulations MCP server safe to use?

Fda Regulations scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Fda Regulations MCP server expose?

Fda Regulations exposes 2 tools: fda_regulation, fda_search. Their descriptions and schemas cost roughly 650 tokens of context every time the server is loaded.

Is the Fda Regulations MCP server still maintained?

Fda Regulations is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Fda Regulations MCP server under?

Fda Regulations declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.