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-banking-regulationsWrote 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-banking-regulations/banking-regulations)<a href="https://agentmods.dev/mcp/pipeworx-io/mcp-banking-regulations/banking-regulations"><img src="https://agentmods.dev/badge/mcp/pipeworx-io/mcp-banking-regulations/banking-regulations/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-banking-regulations/banking-regulations"><img src="https://agentmods.dev/badge/mcp/pipeworx-io/mcp-banking-regulations/banking-regulations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
banking-regulations 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.
This is a copy
77% identical to owid — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"banking-regulations": {
"url": "https://gateway.pipeworx.io/banking-regulations/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 ab45e5ef3af4
banking-regulations is an MCP server published in the GitHub repository pipeworx-io/mcp-banking-regulations (0 stars, last pushed 16d 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. It is 77% identical to owid, differing in 4 lines, and is treated as a copy.
Other mcp servers, from other repositories
us-gov-contracts
US state & local government contracts + spending, normalized across jurisdictions — keyless. Remote server at gateway.pipeworx.io.
latam-validate
Validate LatAm IDs: Mexican CLABE, Brazilian CNPJ/CPF checksums + BrasilAPI company/CEP/bank lookups. Remote server at gateway.pipeworx.io.
cftc-cot
CFTC Commitment of Traders (COT) MCP. Remote server at gateway.pipeworx.io.
fcc-regulations
FCC Regulations MCP — US Federal Communications Commission rules (47 CFR). Remote server at gateway.pipeworx.io.
bis
BIS MCP — Bank for International Settlements statistics (no auth). Remote server at gateway.pipeworx.io.
mcp-server
Calculate US household employer (nanny) taxes + run payroll via AI agents. All 50 states. Runs locally from the @nannykeeper/mcp-server npm package. Needs 1 environment variable to run.