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/roccoangelella/PiLinkWrote 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/roccoangelella/pilink/pilink-pilink-local)<a href="https://agentmods.dev/mcp/roccoangelella/pilink/pilink-pilink-local"><img src="https://agentmods.dev/badge/mcp/roccoangelella/pilink/pilink-pilink-local/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/roccoangelella/pilink/pilink-pilink-local"><img src="https://agentmods.dev/badge/mcp/roccoangelella/pilink/pilink-pilink-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pilink-local 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 12d 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
{
"pilink-local": {
"type": "http",
"url": "http://127.0.0.1:3200/sse"
}
}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.
- 12d ago First seen · 6 lines scan A 2e78cca9c65c
pilink-local is an MCP server published in the GitHub repository roccoangelella/PiLink (18 stars, last pushed yesterday), 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
mcp-odoo
Odoo MCP for AI agents — 41 tools, gated writes, multi-instance. Free hosted product: ERPipe (mcp.erpipe.com). Runs locally from the odoo-mcp Python package. Needs 4 environment variables to run.
mcp-memory-server
Hosted memory for AI agents that learns from outcomes — one key across Claude, Cursor & ChatGPT. Runs locally from the @mnemoverse/mcp-memory-server npm package. Needs 2 environment variables to run.
obsidian-everywhere
Graph context, semantic search, guarded edits, and reviewable Git for local Obsidian vaults. Runs locally from the obsidian-everywhere npm package.
anythingllm-mcp
MCP server "anythingllm-mcp" as configured in andreperez/anythingllm-mcp. Runs locally from the anythingllm-mcp Python package.
sticker-mcp
MCP server "sticker-mcp" as configured in asashiki/sticker-mcp. Runs locally from the @asashiki/sticker-mcp npm package.
dsh-mcp-gateway
MCP server "dsh-mcp-gateway" as configured in siddhartha-yz/dsh-mcp-gateway. Runs locally from the dsh-mcp-gateway Python package.