ctx — queryable code graph

● Active

io.github.Eagle-Logic/ctx

Call graphs, blast radius and API-breakage gates. Every answer reports its own completeness.

Category
Data & Analytics
Version
0.28.1
Registry
active
Published
11/15/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 17, 2026

Looks healthy: ctx — queryable code graph is maintained, open source.

Maintained
Active
Last commit 6 days ago (Nov 16, 2026), 3 open issues.
Official registry
Active
Published as io.github.Eagle-Logic/ctx in the official MCP registry, version 0.28.1.
Source
Open source, MIT
Public repository under the MIT licence, 3 stars, 1 forks.
Runs
On your machine
A local cargo package started by your client; it can reach whatever your user account can.
Credentials
None declared
The registry entry declares no required environment variables.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 16, 2026
Stars
3
Forks
1
Last push
Nov 16, 2026
License
MIT

Rustagent-toolsai-agentsblast-radiuscall-graphclaude-codecode-intelligencecode-navigationcoding-agentsdeveloper-toolsjavallm-toolslocal-firstmcpmcp-serverrustrust-clistatic-analysistree-sitter

From the README

ctx *The binary is ctx. The crate is code-context (ctx was taken on crates.io in 2017).* A queryable code graph for coding agents. Not a map you paste at boot — a set of queries an agent runs mid-task: *who calls this, how does execution get here, what breaks if I change it, what must a move touch, does my port still match the original.* One Rust binary. Tree-sitter for Rust, Python, TypeScript/TSX, JavaScript/JSX, Go, Java, and Markdown. No language servers, no embeddings, no index to warm. The graph is a pure function of the source tree — same code in, same answer out — and it builds in ~100 ms, so every query runs against current source. That last line is the whole idea, and it does two jobs. It claims completeness for what ctx read, and it bounds that claim by counting what it never read — macro bodies and static/const initializers, whose contents are not parsed as code. A call hiding in one is absent rather than unresolved, so nothing else would have revealed it. Every other code graph tells you what it found. ctx tells you what it missed — per edge, in aggregate, and with the grep list to check it yourself. It matters because the failure mode of a code graph is silent. A blast radius that comes back short reads exactly like a blast radius that is complete, and an agent cannot tell the difference — so it changes the signature and ships the break.…

Read the full README on GitHub →

The most-starred Data & Analytics servers in the index, with their live-check result.

ServerStarsLast pushLive check
PostHog41,013Nov 2026Needs sign-in
PostHog MCP Server40,870Nov 2026Needs sign-in
Agent-Native Analytics7,735Nov 2026Needs sign-in
TradingMCP5,320Nov 2026Needs sign-in
Jitsu5,138Nov 2026Needs sign-in

ctx — queryable code graph: questions people ask

Is ctx — queryable code graph a remote or a local MCP server?
According to its entry in the official MCP registry, ctx — queryable code graph ships as a local package (cargo) that your client starts on your machine.
Is ctx — queryable code graph safe to use?
Looks healthy: ctx — queryable code graph is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: None declared. Serverdex check of Nov 17, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is ctx — queryable code graph still maintained?
Active: the repository's last commit 6 days ago. Last push Nov 16, 2026, 3 GitHub stars, MIT licence. Read from GitHub on Nov 16, 2026.
How do I add ctx — queryable code graph to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Data & Analytics →

Add the badge to your site

Show visitors that ctx — queryable code graph is listed here — it’s also the link we check for a free listing.

ctx — queryable code graph — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-eagle-logic-ctx?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="ctx — queryable code graph — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![ctx — queryable code graph — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-eagle-logic-ctx?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).