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/japlete/md-vision-mcpWrote 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/japlete/md-vision-mcp/md-vision)<a href="https://agentmods.dev/mcp/japlete/md-vision-mcp/md-vision"><img src="https://agentmods.dev/badge/mcp/japlete/md-vision-mcp/md-vision/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/japlete/md-vision-mcp/md-vision"><img src="https://agentmods.dev/badge/mcp/japlete/md-vision-mcp/md-vision.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
md-vision 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
{
"md-vision": {
"command": "npx",
"args": [
"-y",
"md-vision"
],
"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.
- 1mo ago First seen · 10 lines scan A e7b0bfc5938b
md-vision is an MCP server published in the GitHub repository japlete/md-vision-mcp (1 stars, last pushed 4mo 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
darwin-rag
Local-first RAG knowledge base with hybrid search (BM25 + embeddings), exposed to AI agents via MCP — fully offline-capable. Runs locally from the darwin-rag Python package. Needs 4 environment variables to run.
rag-knowledge-graph-mcp
Rag Knowledge Graph automation via MCP. Includes index document, rag query, add graph edge. By MEOK AI Labs. Runs locally from the rag-knowledge-graph-mcp Python package.
rag-knowledge-mcp
MCP server for rag knowledge. Features semantic search, knowledge graph query, index document. From MEOK AI Labs. Runs locally from the rag-knowledge-mcp Python package.
ragbuddy
MCP server "ragbuddy" as configured in azmirizkifar20/RAGBuddy. Runs locally from the ragbuddy npm package.
ragflow-claude-mcp
MCP server "ragflow-claude-mcp" as configured in norandom/ragflow-claude-desktop-local-mcp. Runs locally from the ragflow-claude-mcp Python package.
inkdex
MCP server that indexes markdown docs and exposes hybrid semantic search for LLM context retrieval. Runs locally from the inkdex npm package.