Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/zubi-wiz/regmd-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/zubi-wiz/regmd-mcp/regmd-mcp)<a href="https://agentmods.dev/mcp/zubi-wiz/regmd-mcp/regmd-mcp"><img src="https://agentmods.dev/badge/mcp/zubi-wiz/regmd-mcp/regmd-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/zubi-wiz/regmd-mcp/regmd-mcp"><img src="https://agentmods.dev/badge/mcp/zubi-wiz/regmd-mcp/regmd-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
regmd-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "regmd-mcp": { "command": "npx", "args": [ "-y", "regmd-mcp" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 9 lines scan A a0136d0aa7a1
regmd-mcp is an MCP server published in the GitHub repository zubi-wiz/regmd-mcp (1 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
openfda-mcp-server
Query FDA data on drugs, food, devices, and recalls via openFDA. STDIO or Streamable HTTP. Runs locally from the @cyanheads/openfda-mcp-server npm package. Needs 8 environment variables to run.
cosmetic-regulatory
Cosmetic safety: NOAEL, MoS, SCCS, 12 jurisdictions. 30K ingredients. Free. Remote server at roots-mcp-server.rootsbybenda.workers.dev.
fda
FDA MCP — US Food and Drug Administration public API (free, no auth). Remote server at gateway.pipeworx.io.
apple-health-mcp
Query and analyze Apple Health CSV exports using DuckDB. Runs locally from the @neiltron/apple-health-mcp npm package. Needs 3 environment variables to run.
iso27001-mcp
ISO 27001 compliance workspace for Claude. Risks, policies, SoA, evidence, and audit workflows. Runs locally from the iso27001-mcp npm package. Needs 4 environment variables to run.
molecare-mcp
Educational dermatology knowledge and lesion tooling. No credentials needed. Not a medical device. Runs locally from the molecare-mcp npm package. Needs 5 environment variables to run.