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.
npx agentmods add mcp/derkcc/watchcheck/watchcheck-from-sourcegit clone --depth 1 https://github.com/derkcc/watchcheckGrade A, and why
watchcheck-from-source 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 2d 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
{
"watchcheck-from-source": {
"command": "uv",
"args": [
"--directory",
"/absolute/path/to/watchcheck",
"run",
"watchcheck"
]
}
}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.
- 2d ago First seen · 11 lines scan A fb2b5876146b
watchcheck-from-source is an MCP server published in the GitHub repository derkcc/watchcheck (1 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-08-31.
Other mcp servers, from other repositories
oysterworkflow
MCP server "oysterworkflow" as configured in ShuxinYang111/oysterworkflow. Runs ./mcp/server.mjs with node.
imessage-mcp
Read-only MCP for iMessage, SMS, MMS, and RCS history already present in Apple Messages on Mac. Runs locally from the imessage-mcp npm package. Needs 6 environment variables to run.
s-gw
MCP server "s-gw" as configured in sgateway/s-gw. Runs ./dist/mcp-server.js with node. Needs 2 environment variables to run.
plonk
MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR. Runs locally from the plonk-mcp npm package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
codex-computer-use-mcp
Expose the official macOS Computer Use tools directly to Pi and MCP clients without a nested model. Runs locally from the codex-computer-use-mcp npm package.