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/mhoedt-ai/PLwCWrote 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/mhoedt-ai/plwc/plwc-gateway)<a href="https://agentmods.dev/mcp/mhoedt-ai/plwc/plwc-gateway"><img src="https://agentmods.dev/badge/mcp/mhoedt-ai/plwc/plwc-gateway/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/mhoedt-ai/plwc/plwc-gateway"><img src="https://agentmods.dev/badge/mcp/mhoedt-ai/plwc/plwc-gateway.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
plwc-gateway 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.
What it actually says
{
"plwc-gateway": {
"command": "https://github.com/mhoedt-ai/PLwC/releases/download/v0.2.0-rc18.dev9/plwc-gateway-0.2.0-rc18.dev9.mcpb",
"args": [],
"env": {}
}
}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 · 7 lines scan A 9e026ef2e74c
plwc-gateway is an MCP server published in the GitHub repository mhoedt-ai/PLwC (3 stars, last pushed today), licensed Apache-2.0. 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
loomiomcp
Model Context Protocol server for Loomio. Lets Claude (Desktop, Code, or web Projects via Custom Connector) read and create Loomio discussions, polls, and comments, manage group memberships, and analyse member activity in plain English. Runs locally from the loomiomcp npm package.
uap-pulse
Search and map the Pentagon UAP/UFO releases plus curated official archives from 12 nations. Runs locally from the uap-pulse npm package.
comem
Local MCP server for append-only multi-agent coordination memory with an integrator-owned accepted projection and goal-level acceptance contracts. Runs locally from the coordination-memory-mcp Python package.
contextengine
MCP server "contextengine" as configured in FASTPROD/ContextEngine. Runs dist/index.js with node. Needs 1 environment variable to run.
corerag-system
MCP server "corerag-system" as configured in TJ-Neary/CoreRag. Runs locally from the corerag-system Python package.
nornr
MCP server "nornr" as configured in NORNR/nornr-mcp-control. Runs /absolute/path/to/nornr_mcp_control.py with python3. Needs 3 environment variables to run.