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/ProgenyAlpha/reddit-lurkerWrote 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/progenyalpha/reddit-lurker/lurk)<a href="https://agentmods.dev/mcp/progenyalpha/reddit-lurker/lurk"><img src="https://agentmods.dev/badge/mcp/progenyalpha/reddit-lurker/lurk/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/progenyalpha/reddit-lurker/lurk"><img src="https://agentmods.dev/badge/mcp/progenyalpha/reddit-lurker/lurk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lurk 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 9d 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
{ "lurk": { "command": "npx", "args": [ "-y", "reddit-lurker" ], "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.
- 9d ago First seen · 10 lines scan A 2b4518fb9ef0
lurk is an MCP server published in the GitHub repository ProgenyAlpha/reddit-lurker (2 stars, last pushed 19d 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
timps-swarm
161 AI agents for code gen, health, AI/ML, infra, India-stack. One command. Runs locally from the timps-swarm npm package. Needs 10 environment variables to run.
magisterium-mcp-server
MCP server "magisterium-mcp-server" as configured in JacobStephens2/magisterium-mcp-server. Runs locally from the magisterium-mcp-server npm package.
tiny-go-mcp
MCP server "tiny-go-mcp" as configured in kioie/tiny-go-mcp-server. Runs in Docker (ghcr.io/kioie/tiny-go-mcp:1.1.2).
tg-mcp
Local MCP server for your Telegram personal account — channels, digests, messaging, folders and more. Runs locally from the tg-mcp npm package.
jailbreak-mcp
A MCP server wrapper for using the entire Model Context Protocol without tool limits, missing concepts, or context overload. Runs locally from the jailbreak-mcp npm package.
kaiten-mcp
MCP server for Kaiten — 63 tools across cards, comments, checklists, time-tracking, members, blockers, sprints, custom properties, external links, file uploads, location history, and global timesheet. Forked from iamtemazhe/mcp-kaiten with extensive Wave. Runs locally from the kaiten-mcp npm package.