gograph runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 17 Sep 2026.
Local Go repository call graphs and structural analysis for coding agents over stdio.
We read the source, 18 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
serverPath := filepath.Join(root, releaseServerFile)
<script src="https://giscus.app/client.js"
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
MCP server for Instagit — AI-powered Git repository analysis for coding agents
Cross-repository semantic code intelligence for AI coding agents, from a local code graph.
Zero-LLM structural code retrieval for AI coding agents, served over MCP.
Local read-only repository context retrieval for AI coding agents.
Local code-memory graph for AI coding agents.
A graph-native code repository for people and AI agents.
Deterministic AGENTS.md and repo analysis for coding agents, paid per call in USDC over x402.
Codebase graphs, caller impact analysis, and recorded project context for AI coding agents.
Answers built from our own checks of this server.