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/nicofains1/agentwatchWrote 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/nicofains1/agentwatch/agentwatch)<a href="https://agentmods.dev/mcp/nicofains1/agentwatch/agentwatch"><img src="https://agentmods.dev/badge/mcp/nicofains1/agentwatch/agentwatch/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/nicofains1/agentwatch/agentwatch"><img src="https://agentmods.dev/badge/mcp/nicofains1/agentwatch/agentwatch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentwatch 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
{ "agentwatch": { "command": "npx", "args": [ "-y", "@nicofains1/agentwatch" ], "env": { "AGENTWATCH_DB": "" } } }
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 · 12 lines scan A 12859796b5a0
agentwatch is an MCP server published in the GitHub repository nicofains1/agentwatch (1 stars, last pushed 6mo 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
XcodeBuildMCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities. Runs locally from the xcodebuildmcp npm package. Needs 4 environment variables to run.
sentry
Sentry's hosted MCP server: lets the agent search and read issues, errors and traces. Remote server at mcp.sentry.dev.
codecalc
Universal code + logic calculator for AI models: execute 31 languages, evaluate logic, analyze complexity. Exposed via MCP. Runs locally from the codecalc Python package.
vynix-mcp
Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis. Runs locally from the @usevynix/mcp-server npm package. Needs 2 environment variables to run.
mcp-read-only-grafana
MCP server "mcp-read-only-grafana" as configured in lukleh/mcp-read-only-grafana. Runs locally from the . Python package.
starlink-blade-mcp
Starlink dish MCP server — local gRPC monitoring, alerts, and control. Runs locally from the starlink-blade-mcp Python package.