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/keesan12/martin-loop/mcp-martin-loopgit clone --depth 1 https://github.com/Keesan12/martin-loopWrote 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/keesan12/martin-loop/mcp-martin-loop)<a href="https://agentmods.dev/mcp/keesan12/martin-loop/mcp-martin-loop"><img src="https://agentmods.dev/badge/mcp/keesan12/martin-loop/mcp-martin-loop.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
martin-loop 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.
This is a copy
89% identical to martin-loop — 5 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
{
"martin-loop": {
"command": "npx",
"args": [
"-y",
"@martinloop/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.
- 4d ago First seen · 10 lines scan A af03378e74cb
martin-loop is an MCP server published in the GitHub repository Keesan12/martin-loop (47 stars, last pushed 4d ago), 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. It is 89% identical to martin-loop, differing in 5 lines, and is treated as a copy.
Other mcp servers, from other repositories
aegis
Auto-instrument AI agent frameworks with runtime security. One line to govern LangChain, CrewAI, OpenAI, Anthropic — injection blocking, PII masking, action policy, audit trail. Zero code changes. Runs locally from the agent-aegis Python package. Needs 1 environment variable to run.
dingdawg-code-review
AI code review — security, quality, performance. Learns your patterns. Receipted. Runs locally from the dingdawg-code-review npm package. Needs 1 environment variable to run.
dingdawg-data-agent
AI data agent — schema analysis, query optimization, PII detection, pipelines. Runs locally from the dingdawg-data-agent npm package. Needs 1 environment variable to run.
dingdawg-devops-agent
DevOps AI. Deploy checks, incident analysis, infra audit. Learns from past failures. Runs locally from the dingdawg-devops-agent npm package. Needs 1 environment variable to run.
dingdawg-legal-agent
AI contract review, clause drafting, compliance checklists & legal research. Runs locally from the dingdawg-legal-agent npm package. Needs 1 environment variable to run.
dingdawg-marketing-agent
AI content generation, SEO audits, campaign planning & social scheduling. Runs locally from the dingdawg-marketing-agent npm package. Needs 1 environment variable to run.