endiagram
Related Servers
Alternatives to endiagram
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceProvides systems thinking models as composable analysis lenses for architecture, infrastructure, DevOps, incident analysis, and technical decision-making.51-
- FlicenseNot gradedqualityCmaintenanceLets AI agents query a computerized system inventory as a knowledge graph using Cypher, enabling blast radius, data lineage, regulation checks, and change impact assessments while preventing hallucinated regulatory claims.-
- AlicenseBqualityCmaintenanceWhole-repo code graph for AI agents: impact analysis, dead code, cycles, semantic code search — 14 tools via hosted MCP endpoint.15MIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables AI agents to traverse SysML v2 model graphs, query requirements, and perform impact analysis for model-based systems engineering. It allows agents to interact with plain-text models to automate documentation and refine system architectures.-

Gridlaceofficial
AlicenseNot gradedqualityBmaintenanceEnables deterministic dependency reasoning over declared graphs, allowing users and AI agents to validate acyclicity, resolve targets, identify runnable parallel layers, assess impact, and explain blockers.Apache 2.0- FlicenseAqualityAmaintenanceDeterministic code intelligence engine — indexes 27 languages into a queryable symbol graph for real-time blast-radius analysis, no embeddings or LLM calls.524-
TDQS
Scored across 12 tools
Most tools target distinct graph operations, but trace, distance, and between all revolve around paths and centrality, while analyze_system, detail, and categorize overlap in structural analysis. Descriptions help but an agent could reasonably pick the wrong tool for some analytical tasks.
Tool names are mostly single lowercase words, but they mix verbs, nouns, and prepositions (between, distance, impact, detail), and analyze_system breaks the pattern with snake_case. There is no consistent verb_noun or predictable naming convention.
Twelve tools is well-scoped for a dependency-graph analysis server. Each tool has a recognizable responsibility within analysis, rendering, transformation, and composition, without feeling padded or thin.
The toolkit covers traversal, centrality, structural diffing, subsystem discovery, deep analysis, rendering, merging, and dry-run evolution. Minor gaps like explicit node creation/deletion or cycle detection exist, but the server's analytical focus is well covered.