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.
npx agentmods add mcp/codeforstartups/pinpole-mcp/pinpolegit clone --depth 1 https://github.com/codeforstartups/pinpole-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/codeforstartups/pinpole-mcp/pinpole)<a href="https://agentmods.dev/mcp/codeforstartups/pinpole-mcp/pinpole"><img src="https://agentmods.dev/badge/mcp/codeforstartups/pinpole-mcp/pinpole.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
pinpole 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 2d 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
{
"pinpole": {
"command": "npx",
"args": [
"-y",
"@pinpole/mcp"
],
"env": {
"PINPOLE_API_TOKEN": "${PINPOLE_API_TOKEN}",
"PINPOLE_BASE_URL": "https://app.pinpole.cloud"
}
}
}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.
- 2d ago First seen · 13 lines scan A 3773c54d7298
pinpole is an MCP server published in the GitHub repository codeforstartups/pinpole-mcp (0 stars, last pushed 2mo 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
dataproc
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package. Needs 2 environment variables to run.
proximo-proxmox
The Proxmox MCP you can hand the keys: VE/PBS/PMG/PDM. Plan, prove, undo, diagnose. MCP/A2A/API. Runs locally from the proximo-proxmox Python package.
ssh-licco
SSH Model Context Protocol Server - Enable SSH functionality for AI models. Runs locally from the ssh-licco Python package. Needs 4 environment variables to run.
cloudflare-docs
MCP server "cloudflare-docs", hosted remotely at docs.mcp.cloudflare.com, as configured in ourobx/agent-ebpf.
vmware-privateai
VMware Private AI Foundation with NVIDIA ops — GPU inventory, vGPU/DirectPath profiles, utilization, model-serving (MCP + CLI). Runs locally from the vmware-privateai Python package.
project-bourne
Run reproducible scientific workloads on GPUs, local compute, Slurm, and PBS with provenance. Runs locally from the @project-bourne/mcp npm package.