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/varun29ankuS/mif-specWrote 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/varun29ankus/mif-spec/mif-tools)<a href="https://agentmods.dev/mcp/varun29ankus/mif-spec/mif-tools"><img src="https://agentmods.dev/badge/mcp/varun29ankus/mif-spec/mif-tools/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/varun29ankus/mif-spec/mif-tools"><img src="https://agentmods.dev/badge/mcp/varun29ankus/mif-spec/mif-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mif-tools 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 2mo 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
{
"mif-tools": {
"command": "uvx",
"args": [
"mif-tools"
],
"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.
- 2mo ago First seen · 9 lines scan A 6f05ff2e3541
mif-tools is an MCP server published in the GitHub repository varun29ankuS/mif-spec (5 stars, last pushed 8mo 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. 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
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
total-agent-memory
Persistent local memory MCP server for Claude Code, Codex CLI, Cursor and any MCP client: 79 tools — temporal knowledge graph, procedural memory, episodic memory, AST codebase ingest, pre-edit guard, auto-consolidating error capture. Runs locally from the total-agent-memory Python package.
ai-memory
MCP server "ai-memory" as configured in alphaonedev/ai-memory-mcp. Runs in Docker (ghcr.io/alphaonedev/ai-memory:0.5.1). Needs 1 environment variable to run.
local-memory-mcp
Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys. Runs locally from the @studiomeyer/local-memory-mcp npm package. Needs 4 environment variables to run.
awareness-local
Local-first persistent memory for AI coding agents - 96.0% R@5 on LongMemEval, zero LLM calls. Runs locally from the @awareness.market/local npm package.
genome
DNA-inspired memory layer for AI agents: zero-LLM-call ingestion, retrieval that beats full-context on overflowing histories. Runs locally from the genome-memory Python package.