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/pipeworx-io/pipeworxWrote 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/pipeworx-io/pipeworx/pipeworx-catalog)<a href="https://agentmods.dev/mcp/pipeworx-io/pipeworx/pipeworx-catalog"><img src="https://agentmods.dev/badge/mcp/pipeworx-io/pipeworx/pipeworx-catalog/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/pipeworx-io/pipeworx/pipeworx-catalog"><img src="https://agentmods.dev/badge/mcp/pipeworx-io/pipeworx/pipeworx-catalog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pipeworx-catalog 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pipeworx-catalog — 100% identical, 0 lines differ
What it actually says
{
"pipeworx-catalog": {
"url": "https://gateway.pipeworx.io/pipeworx-catalog/mcp",
"type": "streamable-http"
}
}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 · 6 lines scan A e6f31739124b
pipeworx-catalog is an MCP server published in the GitHub repository pipeworx-io/pipeworx (6 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
memorix
Local-first project memory with legacy MCP and 2026 discovery compatibility. Runs locally from the memorix npm package.
fetch
Lets the agent fetch a URL and read its content as markdown. Runs locally from the mcp-server-fetch Python package.
nodejs-api-docs
An MCP Server for Node.js API documentation. Runs locally from the mcp-server-nodejs-api-docs npm package.
transcriptor-mcp
MCP server "transcriptor-mcp" as configured in samson-art/transcriptor-mcp. Runs in Docker (docker.io/artsamsonov/transcriptor-mcp:1.2.4).
better-telegram-mcp
Production-grade MCP server for Telegram — dual-mode Bot API + MTProto, domain-separated tools. Runs locally from the better-telegram-mcp Python package. Needs 3 environment variables to run.
solana-mcp-vybe
MCP server "solana-mcp-vybe", hosted remotely at mcp.vybenetwork.xyz, as configured in vybenetwork/solana-mcp-vybe.