Keystone
Related Servers
Alternatives to Keystone
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceIngests any GitHub repository's code into a Neo4j knowledge graph and exposes it as read-only MCP tools, enabling users to query repo structure, dependencies, and function details via natural language.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to query a parsed graph of a repository and to recall what earlier sessions learned about it, both stored in FalkorDB behind one traversal. It exposes eight MCP tools over stdio for locating symbols, tracing calls and impact paths, and writing or recalling user- and repo-scoped facts, procedures, and handoffs.126,812 npmMIT
- AlicenseNot gradedqualityCmaintenanceDev intelligence layer that builds a knowledge graph from any codebase and exposes 7 MCP tools for graph-powered reasoning, impact analysis, and preflight safety and governance checks.723 PyPI32Apache 2.0
- AlicenseNot gradedqualityAmaintenanceProvides MCP tools to search, compare, and get recommendations for open-source projects from a structured knowledge graph of GitHub data.MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for indexing source code from repositories into a Neo4j graph database and enabling Graph RAG-based search and traversal of functions via natural language queries.-
- AlicenseNot gradedqualityAmaintenanceMCP server for persistent code exploration and diff-aware review, exposing explore and review tools to map call paths, blast radius, and generate explainable risk-scored reports.3 npm2MIT
TDQS
Scored across 15 tools
Each tool targets a distinct resource or analysis angle: single-module risk vs portfolio risk, current knowledge holders vs multi-hop successors, keystone ranking vs per-person counterfactual. Descriptions explicitly state when to use which, so an agent can reliably select among closely related tools.
All names use lowercase snake_case with no camelCase mixing, and they are broadly descriptive. However, the set mixes verb-led commands (draft_actions, find_modules, note_finding) with noun-led queries (overview, keystones, knowledge_map, successors), so the pattern is not a uniform verb_noun convention.
15 tools fit a rich domain spanning graph overview, module discovery, risk analysis, person impact, counterfactuals, memory recall, review workflow, and artifact drafting. Each tool appears to serve a distinct part of the succession-planning workflow without obvious redundancy.
The surface covers discovery, analysis, planning, review, memory, and artifact generation, with no major dead ends. Minor gaps exist around explicit decision management (e.g., listing or approving decisions outside recall) and direct person/module listing, but core workflows are well covered.