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/Partha-SUST16/mcp_monitorWrote 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/partha-sust16/mcp_monitor/mcp-monitor)<a href="https://agentmods.dev/mcp/partha-sust16/mcp_monitor/mcp-monitor"><img src="https://agentmods.dev/badge/mcp/partha-sust16/mcp_monitor/mcp-monitor/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/partha-sust16/mcp_monitor/mcp-monitor"><img src="https://agentmods.dev/badge/mcp/partha-sust16/mcp_monitor/mcp-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-monitor 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
{ "mcp-monitor": { "command": "npx", "args": [ "-y", "@partha-sust16/mcp-monitor" ] } }
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 09df32e4bc06
mcp-monitor is an MCP server published in the GitHub repository Partha-SUST16/mcp_monitor (3 stars, last pushed 17d 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
fleetwright
Work leases in one SQLite file, so a fleet of agents divides a job list instead of racing it. Library, CLI and MCP server, zero dependencies. Runs locally from the fleetwright Python package.
redmine-mcp-server
MCP server that lets AI assistants manage Redmine issues, projects, wikis, and time tracking. Runs locally from the redmine-mcp-server Python package. Needs 12 environment variables to run.
nightgate-mcp
MCP server exposing NIGHTGATE (Midnight blockchain attestation layer) to AI agents. Runs locally from the @odatano/nightgate-mcp npm package.
gitlab-duo-mcp-bridge
MCP server that wraps the GitLab Duo CLI as a clean, fault-tolerant duoreview tool for AI coding agents. Runs locally from the gitlab-duo-mcp-bridge npm package.
mcp-brandfetch
MCP server "mcp-brandfetch" as configured in djmoore711/brandfetch-mcp. Runs locally from the mcp-brandfetch Python package.
wormhole
The Inter-Agent Context Bridge - MCP server for shared agent memory. Runs locally from the wormhole-mcp npm package.