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/helinakdogan/agentmagnetWrote 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/helinakdogan/agentmagnet/agent-magnet)<a href="https://agentmods.dev/mcp/helinakdogan/agentmagnet/agent-magnet"><img src="https://agentmods.dev/badge/mcp/helinakdogan/agentmagnet/agent-magnet/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/helinakdogan/agentmagnet/agent-magnet"><img src="https://agentmods.dev/badge/mcp/helinakdogan/agentmagnet/agent-magnet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-magnet 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 1mo 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
{
"agent-magnet": {
"command": "uvx",
"args": [
"agent-magnet"
],
"env": {
"MAGNET_USER_ID": "",
"MAGNET_OPENAI_KEY": "",
"MAGNET_LOCAL_MODE": "",
"MAGNET_REDIS_URL": "",
"MAGNET_PROJECT_ID": "",
"MAGNET_PROFILE": ""
}
}
}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.
- 1mo ago First seen · 16 lines scan A 9228bc3d601b
agent-magnet is an MCP server published in the GitHub repository helinakdogan/agentmagnet (14 stars, last pushed 1mo 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-30.
Other mcp servers, from other repositories
memory
Gives the agent a persistent knowledge graph it can write facts to and recall across sessions. Runs locally from the @modelcontextprotocol/server-memory npm package.
cogmemory-mcp
CogMemory MCP Server — Unified context subsystems for AI coding agents. Runs locally from the cogmemory-mcp npm package.
context-book-mcp
Stop re-explaining yourself to Agents. Give it the right context, right when needed. Remote server at context-book-mcp-production.up.railway.app.
kiagent
Your mail, chats and documents indexed into a local SQLite corpus, served to AI clients over MCP. Remote server at {subdomain}.localkiagent.com.
reflect-mcp
Reflection's autonomous runtime — wake, read prior state, do useful work, write back, sleep. Runs locally from the reflect-mcp Python package.
mcp
Memory the human governs, on their own machine, plus what other coding agents here wrote. Runs locally from the @mnemosyne_os/mcp npm package. Needs 3 environment variables to run.