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/Liyuchen0118/RunBeaconWrote 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/liyuchen0118/runbeacon/remote-job-monitor)<a href="https://agentmods.dev/mcp/liyuchen0118/runbeacon/remote-job-monitor"><img src="https://agentmods.dev/badge/mcp/liyuchen0118/runbeacon/remote-job-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/liyuchen0118/runbeacon/remote-job-monitor"><img src="https://agentmods.dev/badge/mcp/liyuchen0118/runbeacon/remote-job-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
remote-job-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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- remote-job-monitor — 100% identical, 0 lines differ
What it actually says
{
"remote-job-monitor": {
"command": "node",
"args": [
"./dist/mcp/lifecycle-server.js"
],
"env": {
"MCP_SERVER_MODE": "true"
},
"startup_timeout_sec": 20,
"tool_timeout_sec": 86400
}
}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.
- 12d ago First seen · 13 lines scan A c194b73707cb
remote-job-monitor is an MCP server published in the GitHub repository Liyuchen0118/RunBeacon (2 stars, last pushed 3d 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
taskswarm
Self-hosted event server that pushes a notification the instant a parallel coding-agent session blocks, needs review, fails, or finishes. Runs locally from the taskswarm-cli Python package.
tailscale-mcp
MCP server for safe programmatic access to the local Tailscale daemon: tailnet discovery, SSH config generation, port sharing via Serve/Funnel, and latency matrices. Runs locally from the @tmhs/tailscale-mcp npm package.
lsp
MCP server "lsp" as configured in blackwell-systems/agent-lsp. Launched with agent-lsp go:gopls.
chist
MCP server "chist" as configured in hiropon164/chist-server. Runs locally from the chist Python package.
rewynd
MCP server "rewynd" as configured in SrinjoyDev/rewynd. Launched with rewynd mcp.
mcp-bash-server
MCP server "mcp-bash-server" as configured in uditk2/mcp-bash-server. Runs locally from the mcp-bash-server Python package.