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/jvgomg/podkitWrote 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/jvgomg/podkit/graphify)<a href="https://agentmods.dev/mcp/jvgomg/podkit/graphify"><img src="https://agentmods.dev/badge/mcp/jvgomg/podkit/graphify/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/jvgomg/podkit/graphify"><img src="https://agentmods.dev/badge/mcp/jvgomg/podkit/graphify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
graphify 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 today.
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
{
"graphify": {
"command": "mise",
"args": [
"exec",
"--",
"graphify-mcp",
"--graph",
"graphify-out/graph.json"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- today First seen · 12 lines scan A 5646e419897c
graphify is an MCP server published in the GitHub repository jvgomg/podkit (42 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-09-09.
Other mcp servers, from other repositories
octocode
AI-powered code indexer with semantic search and knowledge graphs. Runs locally from the @muvon/octocode npm package.
qdrant-search
MCP server "qdrant-search", hosted remotely, as configured in nick-pape/grackle.
semantic-search-mcp
RAG-lite: local semantic search over your files, as a CLI and an MCP server. No LLM, no API keys, no servers. Runs locally from the @adborroto/semantic-search-mcp npm package.
rag-db-advisor
MCP server "rag-db-advisor" as configured in kenimo49/rag-db-advisor. Runs locally from the rag-db-advisor Python package.
vectorlane
Open-source local vector memory engine for AI agents — ingest documents, chunk content, generate embeddings, search locally, return metadata/citations. Runs locally from the @talocode/vectorlane npm package.
cognis-ragkit
MCP server "cognis-ragkit" as configured in cognis-digital/ragkit. Runs locally from the cognis-ragkit Python package.