Treering runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 3 Oct 2026.
A local map of your codebase over time: symbols, callers, subgraphs and structural change.
We read the source, 5 d ago · rules 995398eba69f
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.
var start = new ProcessStartInfo(file) { RedirectStandardOutput = true, UseShellExecute = false };
WHERE e.{near} IN (SELECT id FROM symbol WHERE type_id = $type)
AND +o.type_id IN (SELECT value FROM json_each($others))
select.innerHTML = options.map(([value, label]) => `<option value="${value}">${label}</option>`).join("");
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.
Structural code intelligence over MCP: symbols, callers, imports and blast radius, 40+ languages.
A map of your codebase for AI agents: code graph, search, call paths and change impact. No API key.
Local Go repository call graphs and structural analysis for coding agents over stdio.
Structural graph map of any codebase so LLMs navigate by structure, not guesswork.
Local-first engineering cognition for AI coding agents — persistent memory over your codebase.
Real-time codebase graph for AI assistants: call graphs, dependencies, symbol lookup.
Detect API breaking changes, scan your codebase for impact, and draft the fix. Runs locally.
Structural code intelligence for AI agents: real call graphs, blast radius, and change history.
Answers built from our own checks of this server.