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/agenxy/dibs/claude-code-dibsgit clone --depth 1 https://github.com/Agenxy/dibsWrote 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/agenxy/dibs/claude-code-dibs)<a href="https://agentmods.dev/mcp/agenxy/dibs/claude-code-dibs"><img src="https://agentmods.dev/badge/mcp/agenxy/dibs/claude-code-dibs.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
dibs 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 4d 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
{
"dibs": {
"command": "dibs",
"args": [
"mcp-stdio"
]
}
}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.
- 4d ago First seen · 8 lines scan A f4e79e2d9a29
dibs is an MCP server published in the GitHub repository Agenxy/dibs (2 stars, last pushed today), licensed Apache-2.0. 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
shift-mcp-server
Lightweight coordination layer for multiple AI agents working on the same codebase simultaneously. Runs locally from the @cyanheads/shift-mcp-server npm package. Needs 1 environment variable to run.
bus-mcp
Ergonomic MCP server fronting the self-hosted AlphaHive coordination-bus HTTP API (backend/coordinationbus.py) -- post/read/claim/release/heartbeat/status as MCP tools instead of hand-rolled curl. Fast-follow to the coordination-bus arc, github-mcp-shaped (MCP over an HTTP API). Runs locally from the bus-mcp Python…
tooltrust-scanner
Scans MCP servers for prompt injection, data exfiltration, and privilege escalation. Runs locally from the tooltrust-mcp npm package.
semahash
Content-addressed semantics for multi-agent coordination. When the hash is the word. Runs locally from the semahash Python package.
manifold
MCP server "manifold" as configured in nonchan7720/manifold. Runs in Docker (ghcr.io/nonchan7720/manifold:v1.9.0). Needs 2 environment variables to run.
claude-presence
Minimal MCP server for inter-session coordination between parallel Claude Code instances: presence registry, resource locks, broadcast inbox. Runs locally from the claude-presence npm package.