topos-mcp
Related Servers
Alternatives to topos-mcp
- AlicenseNot gradedqualityDmaintenanceProvides comprehensive code analysis through three MCP servers: static analysis for code quality and security, dependency analysis for package management and vulnerabilities, and complexity analysis for maintainability assessment across multiple programming languages.1MIT
- FlicenseNot gradedqualityDmaintenanceProvides deterministic Python code quality analysis using flake8, mypy, McCabe, and vulture, enabling LLMs to access real linting and type checking results.1-
Related Servers
- AlicenseNot gradedqualityCmaintenanceLive codebase intelligence for AI agents. Import graph PageRank for file importance, git forensics for co-change coupling and fragile code, convention detection across 16 domains, and blast radius analysis.6 npm3Business Source 1.1
- AlicenseAqualityAmaintenanceStructural graph map of any codebase. Scans entities, relationships, and feature flows across 13 languages so LLMs navigate by structure instead of reading everything.6245 PyPI59MIT
- AlicenseNot gradedqualityCmaintenanceTransforms codebases into structural knowledge graphs for AI agents and developers, providing precise architectural awareness and dependency mapping.54MIT
- AlicenseNot gradedqualityAmaintenanceStatic codebase analysis as MCP tools — give AI coding agents a map of your repo instead of letting them burn half their tokens rediscovering it file by file.32 npmMIT
- AlicenseBqualityCmaintenanceWhole-repo code graph for AI agents: impact analysis, dead code, cycles, semantic code search — 14 tools via hosted MCP endpoint.15MIT
- AlicenseNot gradedqualityAmaintenanceProvides a dependency graph of any local repository with tools for change impact, transitive dependents, health audits, and more, enabling AI coding agents to see structure and refactor safely.4,912 npm4MIT
TDQS
Scored across 17 tools
Each tool has a clearly distinct purpose: assess_* variants target different comparison contexts (changeset, side-by-side variant, snapshot, worktree), evaluate_* target different scopes (code, file, project), compare_* target string vs file inputs, and the rest (preference walk, depgraph status/generation, docs, inspect, refactor, begin refactor, coverage) are all unique. No two tools appear to do the same thing.
All tools follow the consistent `topos_` prefix with snake_case and a verb-first pattern: assess_*, evaluate_*, compare_*, plus standalone verbs like inspect, refactor, begin, calculate, generate. The naming is uniform in style and clearly groups related operations.
17 tools is slightly above the typical 3-15 sweet spot, but the scope is broad (evaluation, assessment, comparison, graph management, documentation, coverage, refactoring). Each tool serves a distinct workflow step, so the count is justified without feeling bloated.
The tool surface covers the main lifecycle: evaluating code/files/projects, comparing variants, assessing changes in multiple baseline scenarios, generating and checking dependency graphs, inspecting details, calculating coverage, and obtaining documentation. Minor gaps exist (e.g., no snapshot listing or deletion, no explicit commit-level assessment), but agents can complete core workflows without dead ends.