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/malkreide/bag-epl-mcpInstalling this writes the configuration, not the program: `python` runs a file from the repository, so clone it first and make the path in the command match where you put it.
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/malkreide/bag-epl-mcp/bag-epl)<a href="https://agentmods.dev/mcp/malkreide/bag-epl-mcp/bag-epl"><img src="https://agentmods.dev/badge/mcp/malkreide/bag-epl-mcp/bag-epl/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/malkreide/bag-epl-mcp/bag-epl"><img src="https://agentmods.dev/badge/mcp/malkreide/bag-epl-mcp/bag-epl.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bag-epl 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 2mo 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
{
"bag-epl": {
"command": "python",
"args": [
"-m",
"bag_epl_mcp.server"
]
}
}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.
- 2mo ago First seen · 9 lines scan A 8f07d59babc1
bag-epl is an MCP server published in the GitHub repository malkreide/bag-epl-mcp (0 stars, last pushed 4d 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
chia-mcp
Licensed US telehealth — GLP-1 medications, intake, consents, Stripe ACP. HIPAA-compliant, 30 tools. Remote server at mcp.chia.health.
parlament
MCP server "parlament" as configured in malkreide/parlament-mcp. Runs parlament_mcp.server with python.
parlament-mcp
MCP server for the Swiss Parliament (Curia Vista OData API). Runs locally from the parlament-mcp Python package.
srgssr
MCP server for SRG SSR public APIs – weather, TV/radio metadata, program guide & Swiss votations/elections since 1900. Runs locally from the srgssr-mcp Python package. Needs 2 environment variables to run.
srgssr-mcp
MCP server for SRG SSR public APIs – weather, TV/radio metadata, program guide & Swiss votations/elections since 1900. Runs locally from the srgssr-mcp Python package.
hcmcp
MCP server "hcmcp" as configured in trionnemesis/healthcare-opendata-mcp. Runs locally from the hcmcp Python package.