mcp server
io.github.Anandb71/arbor
The Graph-Native Intelligence Layer for Code.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Most recent push to the repository was 2026-08-03.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 151 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-03 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 3 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-01-07 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-01-07 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
Grasp — Code Architecture & Dependency Analysis
— last commit 2026-07-17, shares code-analysis, static-analysis, visualization
Codebase analysis: dependency graphs, security scanning, and refactor plans for GitHub and GitLab.
-
ArcadeDB MCP Server
— last commit 2026-08-06, shares graph
Built-in MCP server for ArcadeDB multi-model database (graph, document, vector, time-series)
-
com.clauxel.codegraphcontext/codegraphcontext-mcp
— last commit 2026-05-21, shares graph
A paid remote MCP for code graph MCP for AI coding, built to return verdicts, receipts, usage logs,
-
ArcadeDB
— last commit 2026-08-06, shares graph
Multi-Model database with built-in MCP server for SQL, Cypher, Gremlin, and GraphQL.
-
DevLens
— last commit 2026-07-21, shares code-analysis, visualization
Query a precomputed code graph (nodes, edges, summaries) of TS/JS/React/Next.js/Node repos via MCP.
-
Aptu Coder
— last commit 2026-08-06, shares ast, code-analysis, rust
MCP server for code structure analysis using tree-sitter.
-
Code Analyze MCP
— last commit 2026-08-06, shares ast, code-analysis, rust
MCP server for code structure analysis using tree-sitter.
-
Codebase Memory
— last commit 2026-08-08, shares ast, code-analysis, tree-sitter
Codebase knowledge graph for AI agents — 159 languages, sub-ms queries, 99% fewer tokens.
-
coldstart
— last commit 2026-08-06, shares ast, static-analysis, tree-sitter
Codebase memory for AI agents: an AST index plus agent-written notes that self-stale.
-
io.github.ai-dashboad/flutter-skill
— last commit 2026-07-23, shares flutter
AI-powered E2E testing for 10 platforms. 253 MCP tools. Zero test code needed.
These share tags the maintainers applied themselves, such as code-analysis, static-analysis, visualization, graph. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai-tools, ast, code-analysis, code-analysis-tool, developer-tools, flutter, graph, mcp, model-context-protocol, rust, static-analysis, tree-sitter, visualization.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab