unfragile-mcp-server
Related Servers
Alternatives to unfragile-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI to analyze, query, and manage a graph-based representation of software architecture for impact analysis, dependency tracking, and design.209 npm1AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceRAG Knowledge Graph - MCP server providing AI-powered tools and automation by MEOK AI Labs6 npmMIT
- AlicenseAqualityDmaintenanceA cross-project knowledge graph for MCP that maps features across mobile, backend, and admin codebases, giving AI agents full-stack context.1647 npm1MIT
- FlicenseNot gradedqualityDmaintenanceAI-native code intelligence graph that builds a persistent knowledge graph of your codebase in Neo4j and exposes it to AI assistants via MCP, enabling contextual code analysis, impact analysis, and dependency tracking.23-
- AlicenseNot gradedqualityDmaintenanceEnables sophisticated reasoning workflows using graph-based representations for AI models.11Apache 2.0
- AlicenseBqualityCmaintenanceWhole-repo code graph for AI agents: impact analysis, dead code, cycles, semantic code search — 14 tools via hosted MCP endpoint.15MIT
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: compare artifacts, give feedback, find MCPs, build stacks, get details, resolve capabilities, search, subscribe/unsubscribe, and get trust passports. No two tools overlap in function; descriptions further clarify boundaries.
Tool names consistently use snake_case and descriptive verbs. Most follow a verb_noun pattern (e.g., find_mcps, get_artifact), though a few are single verbs (compare, feedback) or noun_noun (trust_passport). Minor inconsistency but overall predictable.
With 10 tools, the server covers core discovery, comparison, stack building, feedback, and monitoring. The count is well-balanced for the domain—neither sparse nor overwhelming.
The tool surface covers search, comparison, details, trust, stack assembly, MCP discovery, feedback, and subscription management. Minor gaps (e.g., listing all monitors) are non-critical; core workflows are fully supported.