A
licenseNot graded
qualityA
maintenanceAn MCP server that provides a shared graph of an organization's projects, processes, areas, and principles, enabling consistent context for tools and AI agents.
2
Apache 2.0
COS-MCP
Related Servers
Alternatives to COS-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI agents to search, fetch, and analyze a self-maintaining markdown knowledge base with provenance, drift detection, and canonical definitions.1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that connects AI agents to a shared organizational knowledge base, allowing them to query company-specific context like pricing, team, and strategy.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that builds a knowledge graph from code and text documents, enabling Q\&A and implementation planning via tools like graph_create, graph_plan, and graph_query.7MIT
- 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 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
TDQS
A4.1/5.0
Scored across 12 tools
Disambiguation3/5
Several tools overlap around bus factor and ownership analysis. analyze_repository_ownership, analyze_knowledge_risk, and calculate_bus_factor all deal with bus factor at different scopes (repo, org, team), which could cause misselection. identify_hidden_dependencies and build_ownership_graph also have overlapping purposes in surfacing employee responsibilities, though they differ in focus on hidden vs. comprehensive dependencies.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern (e.g., analyze_repository_ownership, calculate_bus_factor, generate_transition_plan). The verbs are distinct and descriptive, making the naming predictable and easy to navigate.
Tool Count5/5
12 tools is well-scoped for the domain of organizational knowledge, bus factor, and transition planning. Each tool serves a distinct functional need, from data ingestion (sync_github_repository, enrich_employee_profile) to analysis (bus factor, ownership graph) to actionable planning (transition plans, onboarding paths). No tool feels redundant or unnecessary.
Completeness4/5
The tool surface covers the core workflow of assessing continuity risk and planning transitions: identify risks (bus factor, hidden dependencies), analyze ownership, find experts, generate transition plans and onboarding paths. Minor gaps include lack of a direct tool to edit or remove organizational knowledge entries, but the existing tools provide sufficient coverage for the primary use case.
Maintenance
ActivityStale
ResponsivenessNo issues