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/di-omics/plr-mcpInstalling this writes the configuration, not the program: `plr-mcp` 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/di-omics/plr-mcp/plr)<a href="https://agentmods.dev/mcp/di-omics/plr-mcp/plr"><img src="https://agentmods.dev/badge/mcp/di-omics/plr-mcp/plr/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/di-omics/plr-mcp/plr"><img src="https://agentmods.dev/badge/mcp/di-omics/plr-mcp/plr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
plr 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
{
"plr": {
"type": "stdio",
"command": "plr-mcp",
"env": {
"PLR_MCP_BACKEND": "chatterbox"
}
}
}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 · 9 lines scan A 2bc627174627
plr is an MCP server published in the GitHub repository di-omics/plr-mcp (0 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-09-01.
Other mcp servers, from other repositories
bernstein
MCP server "bernstein" as configured in sipyourdrink-ltd/bernstein. Launched with bernstein mcp.
martin-loop
MCP server for AI coding agents — verifier gates, stop limits, and Verified Handoffs. Runs locally from the @martinloop/mcp npm package.
termlink
MCP server "termlink" as configured in DimitriGeelen/agentic-engineering-framework. Launched with termlink mcp serve. Needs 2 environment variables to run.
trace
MCP server "trace" as configured in Thru-Echoes/TRACE. Runs locally from the . Python package. Needs 1 environment variable to run.
fw
MCP server "fw" as configured in DimitriGeelen/agentic-engineering-framework. Runs agents/mcp/framework_mcp_server.py with python3.
novyx-mcp
MCP tools for Novyx governed actions, shared memory, audit, rollback, and evidence workflows. Local SQLite memory works zero-config; hosted governance and approvals use Novyx Cloud. Runs locally from the novyx-mcp Python package.