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/nifrajs/nifraWrote 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/nifrajs/nifra/nifra-docs)<a href="https://agentmods.dev/mcp/nifrajs/nifra/nifra-docs"><img src="https://agentmods.dev/badge/mcp/nifrajs/nifra/nifra-docs/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/nifrajs/nifra/nifra-docs"><img src="https://agentmods.dev/badge/mcp/nifrajs/nifra/nifra-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
nifra-docs 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 2mo 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
{
"nifra-docs": {
"url": "https://mcp.nifra.dev",
"type": "streamable-http"
}
}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.
- 2mo ago First seen · 6 lines scan A 6bbc0465b825
nifra-docs is an MCP server published in the GitHub repository nifrajs/nifra (6 stars, last pushed today), 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.
nifra-docs compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| nifra-docsnifrajs/nifra | MCP server | 6 | today | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| veryfrontveryfront/veryfront-code | MCP server | 20 | today | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| plain-exampledropseed/plain | MCP server | 1.0k | 6d ago | none | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| linear-serverinkline/inkline | MCP server | 1.5k | 2mo ago | none | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| usda-mcp-servercyanheads/usda-mcp-server | MCP server | 1 | 16d ago | Apache-2.0 | A | — | Claude Code |
| swarm-mcpVolpestyle/swarm-mcp | MCP server | 1 | 1mo ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| mcpgeocoding-ai/mcp | MCP server | 3 | 1y ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |