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/selfagency/beans-mcpWrote 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/selfagency/beans-mcp/public-beans-mcp)<a href="https://agentmods.dev/mcp/selfagency/beans-mcp/public-beans-mcp"><img src="https://agentmods.dev/badge/mcp/selfagency/beans-mcp/public-beans-mcp/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/selfagency/beans-mcp/public-beans-mcp"><img src="https://agentmods.dev/badge/mcp/selfagency/beans-mcp/public-beans-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
beans-mcp 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.
This is a copy
75% identical to playwright-mcp — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"beans-mcp": {
"command": "npx",
"args": [
"-y",
"@selfagency/beans-mcp"
],
"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 96d4712f4228
beans-mcp is an MCP server published in the GitHub repository selfagency/beans-mcp (0 stars, last pushed 4mo 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. It is 75% identical to playwright-mcp, differing in 4 lines, and is treated as a copy.
Other mcp servers, from other repositories
saga-mcp
Jira-like project tracker for AI agents with SQLite, full task hierarchy, and dashboard. Runs locally from the saga-mcp npm package.
okffs
MCP server connecting Claude Code to GitHub for an issue to branch to PR to close workflow. Runs locally from the @neturely/okffs npm package. Needs 3 environment variables to run.
huly-mcp-server
MCP server for Huly issue tracking with stdio and Streamable HTTP transports. Runs locally from the @bgx4k3p/huly-mcp-server npm package.
trail
Issue tracker and durable project memory for your coding agent, scoped to the folder you open. Runs locally from the usetrail npm package. Needs 2 environment variables to run.
vibeops-tracker
VibeOps Tracker: a local-first issue tracker. Capture, triage, and ship work across all your side projects with an embeddable widget, a Kanban board, markdown storage, and an MCP server that lets AI coding agents work your backlog. Runs locally from the vibeops-tracker npm package.
teamdynamix-mcp
A production-ready TypeScript MCP server for TeamDynamix. Runs locally from the @selfagency/teamdynamix-mcp npm package.