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/LofiFren/PicoCalcWrote 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/lofifren/picocalc/picocalc-mcp)<a href="https://agentmods.dev/mcp/lofifren/picocalc/picocalc-mcp"><img src="https://agentmods.dev/badge/mcp/lofifren/picocalc/picocalc-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/lofifren/picocalc/picocalc-mcp"><img src="https://agentmods.dev/badge/mcp/lofifren/picocalc/picocalc-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
picocalc-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 1mo 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
{ "picocalc-mcp": { "command": "uvx", "args": [ "picocalc-mcp" ], "env": {} } }
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.
- 1mo ago First seen · 9 lines scan A e30a78bd93d1
picocalc-mcp is an MCP server published in the GitHub repository LofiFren/PicoCalc (79 stars, last pushed 14d 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-30.
Other mcp servers, from other repositories
mnemo-mcp
Open-source MCP Server for persistent AI memory with embedded sync. Runs locally from the mnemo-mcp Python package. Needs 1 environment variable to run.
openosint
AI-powered OSINT agent, MCP server, and CLI. Interactive REPL + 19 tools. Anthropic Claude or local Ollama. For authorized security research use only. Runs locally from the openosint Python package. Needs 5 environment variables to run.
waitbus
Workstation-local event bus and blocking wait/emit primitive: let any agent or script wait on or emit CI, pytest, Docker, and filesystem events without polling. GitHub Actions is source #1. Runs locally from the waitbus Python package.
cfast-mcp
MCP server for CFAST (Fire and Smoke Transport), built on top of PyCFAST. Runs locally from the cfast-mcp Python package.
firewalla-mcp
MCP server "firewalla-mcp" as configured in djuntgen/firewalla-mcp. Runs locally from the firewalla-mcp Python package.
mcp-fns-calc
A local MCP server for Russian tax calculations and checks of taxpayer status. It uses a hosted API for fiscal-status checks and needs an access token.