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/mohanagy/madarWrote 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/mohanagy/madar/mcp-registry-madar)<a href="https://agentmods.dev/mcp/mohanagy/madar/mcp-registry-madar"><img src="https://agentmods.dev/badge/mcp/mohanagy/madar/mcp-registry-madar/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/mohanagy/madar/mcp-registry-madar"><img src="https://agentmods.dev/badge/mcp/mohanagy/madar/mcp-registry-madar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
madar 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
{
"madar": {
"command": "npx",
"args": [
"-y",
"@lubab/madar"
],
"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 e8036c086790
madar is an MCP server published in the GitHub repository mohanagy/madar (19 stars, last pushed today), 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-30.
Other mcp servers, from other repositories
context7
Context7's hosted MCP server: up-to-date library documentation and code examples on demand. Remote server at mcp.context7.com.
contextforge-mcp
Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot. Runs locally from the contextforge-mcp npm package. Needs 2 environment variables to run.
recall
Open-source agent-memory MCP server. recall.works. Runs locally from the ai-recallworks Python package.
cubelife
Give AI agents a persistent pixel-art character reflecting their state in real time. Runs locally from the cubelife npm package. Needs 2 environment variables to run.
brand-intelligence
Brand health & trend footprint across PSFK expert graphs with citable sources, not web summaries. Remote server at mcp.fodda.ai.
mobile-mcp-opengl
MCP server "mobile-mcp-opengl" as configured in antonpinchuk/mobile-mcp-opengl. Runs locally from the mobile-mcp-opengl npm package.