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/houtini-ai/google-knowledge-graph-mcp/google-knowledge-graphgit clone --depth 1 https://github.com/houtini-ai/google-knowledge-graph-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/houtini-ai/google-knowledge-graph-mcp/google-knowledge-graph)<a href="https://agentmods.dev/mcp/houtini-ai/google-knowledge-graph-mcp/google-knowledge-graph"><img src="https://agentmods.dev/badge/mcp/houtini-ai/google-knowledge-graph-mcp/google-knowledge-graph.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
google-knowledge-graph 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 5d 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
{
"google-knowledge-graph": {
"command": "npx",
"args": [
"-y",
"@houtini/google-knowledge-graph-mcp"
],
"env": {
"GOOGLE_KNOWLEDGE_GRAPH_API_KEY": ""
}
}
}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.
- 5d ago First seen · 12 lines scan A d75432d462c5
google-knowledge-graph is an MCP server published in the GitHub repository houtini-ai/google-knowledge-graph-mcp (11 stars, last pushed 27d 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
NOUZ-MCP
MCP server for Obsidian — semantic knowledge graph with auto-classification, DAG hierarchy, and cross-domain bridge detection. Runs locally from the nouz-mcp Python package. Needs 8 environment variables to run.
thebrain
MCP server for TheBrain 15: search by meaning, graph traversal and batch writes over the local API. Runs locally from the thebrain-mcp-server npm package. Needs 7 environment variables to run.
wikidata-mcp-server
Search and fetch Wikidata entities, execute SPARQL queries, and resolve external identifiers. Runs locally from the @cyanheads/wikidata-mcp-server npm package. Needs 4 environment variables to run.
LINZA-MCP
Local-first MCP sidecar for agent workspaces, artifacts, review intents, and context export. Runs locally from the linza-mcp Python package. Needs 9 environment variables to run.
mcp-fitbod
MCP server "mcp-fitbod" as configured in Muno459/mcp-fitbod. Runs locally from the mcp-fitbod Python package.
june-mcp
MCP server for Junê — give any MCP agent (Claude Desktop, Claude Code, …) a shared, cited knowledge-graph memory backed by a June endpoint. Runs locally from the june-mcp Python package. Needs 13 environment variables to run.