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/MachuraHarry/pipeInstalling this writes the configuration, not the program: `https://github.com/MachuraHarry/pipe/releases/download/v1.1.0/pipe-docs-server-linux-amd64.mcpb` has to be on your PATH already, or the server will not start.
Wrote 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/machuraharry/pipe/pipe-docs)<a href="https://agentmods.dev/mcp/machuraharry/pipe/pipe-docs"><img src="https://agentmods.dev/badge/mcp/machuraharry/pipe/pipe-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/machuraharry/pipe/pipe-docs"><img src="https://agentmods.dev/badge/mcp/machuraharry/pipe/pipe-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pipe-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 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
{
"pipe-docs": {
"command": "https://github.com/MachuraHarry/pipe/releases/download/v1.1.0/pipe-docs-server-linux-amd64.mcpb",
"args": [],
"env": {}
}
}What else server.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 7 lines scan A 0988a251d1ff
pipe-docs is an MCP server published in the GitHub repository MachuraHarry/pipe (3 stars, last pushed 1mo 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
web-researcher
MCP server "web-researcher" as configured in zoharbabin/web-researcher-mcp. Launched with web-researcher-mcp. Needs 59 environment variables to run.
web-researcher-mcp
MCP server "web-researcher-mcp" as configured in zoharbabin/web-researcher-mcp. Runs in Docker (ghcr.io/zoharbabin/web-researcher-mcp:1.9.0). Needs 8 environment variables to run.
agent-memory
Git-native project memory for AI coding agents: Markdown source of truth, reviewable, secret-safe. Runs locally from the @xchucx/agent-memory npm package.
llmprobe
MCP server "llmprobe" as configured in Jwrede/llmprobe. Launched with llmprobe mcp.
docgraph
MCP server "docgraph" as configured in Detective-XH/DocGraph. Launched with docgraph serve --path ..
memex
MCP server "memex" as configured in kioie/memex. Runs in Docker (ghcr.io/kioie/memex:0.6.0). Needs 3 environment variables to run.