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/RBV801/recipal-mcp-unofficialWrote 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/rbv801/recipal-mcp-unofficial/recipal-mcp-unofficial)<a href="https://agentmods.dev/mcp/rbv801/recipal-mcp-unofficial/recipal-mcp-unofficial"><img src="https://agentmods.dev/badge/mcp/rbv801/recipal-mcp-unofficial/recipal-mcp-unofficial/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/rbv801/recipal-mcp-unofficial/recipal-mcp-unofficial"><img src="https://agentmods.dev/badge/mcp/rbv801/recipal-mcp-unofficial/recipal-mcp-unofficial.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
recipal-mcp-unofficial 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 11d 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
{ "recipal-mcp-unofficial": { "command": "npx", "args": [ "-y", "recipal-mcp-unofficial" ] } }
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.
- 11d ago First seen · 9 lines scan A 6d8370bd6f04
recipal-mcp-unofficial is an MCP server published in the GitHub repository RBV801/recipal-mcp-unofficial (1 stars, last pushed 2d ago), licensed Apache-2.0. 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
yazio-mcp
MCP server for accessing Yazio user & nutrition data (unofficial). Runs locally from the yazio-mcp npm package.
cronometer-mcp
MCP server for Cronometer nutrition data — pull food logs, macros, and micronutrients via the Model Context Protocol. Runs locally from the cronometer-mcp Python package.
usda-mcp
MCP server exposing a USDA-accurate food database with deterministic macro math — no hallucinated nutrition numbers. Runs locally from the usda-mcp Python package.
supstack
Evidence-based supplement research, dosing, safety, and interactions as agent-callable tools. Runs locally from the @supstack/cli npm package.
musette-mcp
AI soigneur for cyclists: Strava ride to an Ien-Vitse-validated nutrition plan + orderable box. Remote server at mcp.musette.cc.
weight-mcp
MCP server "weight-mcp" as configured in CommanderTvis/weight-mcp. Runs locally from the weight-mcp Python package.