PinchMCP
Related Servers
Alternatives to PinchMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server that helps software teams track and understand technical debt, recurring issues, project dependencies, and real-time agent handoffs through a causal knowledge graph.2 npm1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server that extracts and links code, tasks, documentation, and git history into a graph, then diagnoses discrepancies and generates reports.Apache 2.0
- AlicenseNot gradedqualityFmaintenanceAI code impact analysis MCP server that monitors file changes, maps dependency graphs, detects cascading breakage, and gates builds before damage spreads.53 npm2Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server that builds a dependency graph of your codebase, giving AI agents structural understanding to analyze impact, find context, and make safe modifications across languages and infrastructure.14 PyPIMIT

flyto-indexerofficial
AlicenseNot gradedqualityAmaintenanceMCP server that gives AI assistants impact analysis, cross-project reference tracking, and code health scoring.131 PyPI4Apache 2.0- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server that provides a graph database for tracking software codebase components, their relationships, and associated tasks/goals.1MIT
TDQS
Scored across 10 tools
Each tool has a clearly distinct analytical purpose – from ranking keystones to computing critical paths, explaining blockers, suggesting code links/scope, surfacing gaps, grounding features, reconciling notes, listing projects, and rebuilding graphs – with no overlapping or ambiguous boundaries.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., rank_keystones, list_projects, build_feature_graph), with no mixing of conventions or vague verbs.
With 10 tools, the set is well-scoped for a dependency analysis server – enough to cover essential analyses without redundancy or bloat.
The tool surface covers the full analytical lifecycle: project discovery, graph building, multi-angle dependency analysis, coupling inference, gap detection, feature grounding, and meeting note reconciliation – with no obvious gaps given the server's read-only, suggestion-only design.