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/1999azzar/menager-mcp-server/menagergit clone --depth 1 https://github.com/1999AZZAR/menager-mcp-serverWrote 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/1999azzar/menager-mcp-server/menager)<a href="https://agentmods.dev/mcp/1999azzar/menager-mcp-server/menager"><img src="https://agentmods.dev/badge/mcp/1999azzar/menager-mcp-server/menager.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
menager 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 5d 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
{ "menager": { "command": "npx", "args": [ "-y", "menager" ] } }
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.
- 5d ago First seen · 9 lines scan A 66f842617eff
menager is an MCP server published in the GitHub repository 1999AZZAR/menager-mcp-server (0 stars, last pushed 9d 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
hatchet-mcp
Observe and operate Hatchet workflows from an AI agent — runs, logs, trigger, cancel, replay. Runs locally from the hatchet-mcp npm package. Needs 3 environment variables to run.
dispatch-mcp
MCP server "dispatch-mcp" as configured in selamy-labs/dispatch-mcp. Runs locally from the dispatch-mcp Python package.
cicall
MCP server "cicall" as configured in basionwang-bot/cicall. Runs locally from the cicall Python package.
hatchet-mcp
Operational MCP server for Hatchet — read-only by default, with opt-in run control over the Hatchet REST API. Runs locally from the hatchet-mcp Python package.
orgx-mcp
Make AI work resumable, reviewable, and provable across agents. Remote server at mcp.useorgx.com.
claude-session-bridge
MCP message bus that bridges multiple Claude Code sessions (frontend / backend / infra) within a project. Send results from one session, auto-receive them in another. Runs locally from the claude-session-bridge npm package.