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/mcp-f1Wrote 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/mcp-f1/f1)<a href="https://agentmods.dev/mcp/pipeworx-io/mcp-f1/f1"><img src="https://agentmods.dev/badge/mcp/pipeworx-io/mcp-f1/f1/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/mcp-f1/f1"><img src="https://agentmods.dev/badge/mcp/pipeworx-io/mcp-f1/f1.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
f1 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 10d 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
3 near-identical copies found in the catalogue:
- metabolights — 88% identical, 4 lines differ
- zoho_crm — 86% identical, 4 lines differ
- nbu-ua — 86% identical, 4 lines differ
What it actually says
{
"f1": {
"url": "https://gateway.pipeworx.io/f1/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.
- 10d ago First seen · 6 lines scan A 631a4aa966d8
f1 is an MCP server published in the GitHub repository pipeworx-io/mcp-f1 (0 stars, last pushed 15d 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
football-data
Football-Data.org MCP — soccer competitions, matches, standings. Remote server at gateway.pipeworx.io.
outlook-calendar
Outlook Calendar MCP Pack. Remote server at gateway.pipeworx.io.
gitlab-public
GitLab Public MCP — wraps the GitLab REST API v4 (public endpoints, no auth). Remote server at gateway.pipeworx.io.
arcgis-charlotte
City of Charlotte GIS — Charlotte, North Carolina open geospatial data (ArcGIS). Remote server at gateway.pipeworx.io.
opendata-canada
MCP server "opendata-canada", hosted remotely at gateway.pipeworx.io, as configured in pipeworx-io/mcp-opendata-canada.
send-that-email
MCP server "send-that-email", hosted remotely at gateway.pipeworx.io, as configured in pipeworx-io/mcp-send-that-email.