# nikolai-vysotskyi/trace-mcp

Source: https://glimind.com/server/awesome%2Fnikolai-vysotskyi%2Ftrace-mcp
Registry id: `awesome/nikolai-vysotskyi/trace-mcp`
Status: unknown

## Tools (80)

- `assess_change_risk`: Before modifying a file or symbol, predict risk level (low/medium/high/critical) with contributing factors and recommended mitigations. Combines blast radius, c
- `check_architecture`: Check architectural layer rules: detect forbidden imports between layers (e.g. domain importing infrastructure). Supports auto-detected presets (clean-architect
- `check_duplication`: Check if a function/class name already exists before creating it. Pass `name` when planning new code, or `symbol_id` to check an existing symbol against others 
- `detect_drift`: Detect architectural drift: cross-module co-change anomalies (files in different modules that always change together) and shotgun surgery patterns (commits touc
- `detect_topic_tunnels`: Cross-project topic tunnels: links between registered subprojects sharing canonical entities — manifest package names, top-level declared dependencies, and git 
- `diff_graph_snapshots`: Compare two named graph snapshots and report deltas in counts, communities, and top in-degree files. Use to track graph evolution over time without git as the a
- `discover_claude_sessions`
- `discover_hermes_sessions`: List Hermes Agent (NousResearch) sessions visible on this machine. Scans $HERMES_HOME (default ~/.hermes) for state.db plus any profiles/<name>/state.db. Hermes
- `embed_repo`
- `explain_architecture`: AI-powered architecture analysis — layers, patterns, and data flow
- `explain_symbol`: Explain a symbol in detail using AI — purpose, behavior, relationships, usage patterns
- `export_graph`: Export the dependency graph in formats external tools understand. Supports GraphML (Gephi/yEd/NetworkX), Cypher (Neo4j import script), and Obsidian (markdown va
- `find_similar`: Find semantically similar symbols using vector search + optional AI reranking
- `generate_insights_report`
- `get_api_contract`: Get API contract (OpenAPI/gRPC/GraphQL) for a service. Parses spec files found in the service repo. Use to inspect a service's public API. For detecting spec-vs
- `get_api_surface`: List all exported symbols (public API) of a file or matching files. Use to understand what a module exposes. For finding unused exports use get_dead_code with m
- `get_circular_imports`
- `get_code_owners`: Git-based code ownership: who contributed most to specific files (git shortlog). Requires git. Use to identify who to ask about specific files. For symbol-level
- `get_complexity_trend`: File complexity over git history: cyclomatic complexity at past commits. Shows if a file is getting more or less complex. Requires git. Use to track whether a f
- `get_contract_drift`: Detect mismatches between API spec and implementation: endpoints in spec but not in code, or in code but not in spec. Use to verify API contract accuracy. For r
- `get_contract_versions`: Show version history for a service API contract with breaking change detection between versions. Compares request/response schemas across snapshots to flag remo
- `get_coupling`: Coupling analysis: afferent (Ca), efferent (Ce), instability index per file. Shows which modules are stable vs unstable. Use to identify fragile or overly-depen
- `get_coupling_trend`: File coupling over git history: Ca/Ce/instability at past commits. Shows if a module is stabilizing or destabilizing. Requires git. Use to track module stabilit
- `get_cross_domain_deps`: Show which business domains depend on which. Based on edges between symbols in different domains. Use to understand domain coupling. Read-only. Returns JSON: { 
- `get_cross_service_impact`: Analyze cross-service impact of changing an endpoint or event. Shows which services would be affected. Use before modifying a shared endpoint. For within-codeba
- `get_cross_workspace_impact`: Show which workspaces are affected by changes in a given workspace. Lists all cross-workspace edges, affected symbols, and the public API surface consumed by ot
- `get_dataflow`: Intra-function dataflow analysis: track how each parameter flows through the function body — into which calls, where it gets mutated, and what is returned. Phas
- `get_dependency_diagram`: Render dependency diagram for a file/directory path as Mermaid or DOT. Input: a path like "src/tools/" — not a question. Trims to max_nodes most important nodes
- `get_domain_context`: Get all code related to a specific business domain. Supports "parent/child" notation (e.g. "payments/refunds"). Use to explore code within a domain boundary. Fo
- `get_domain_map`: Get hierarchical map of business domains with key symbols per domain. Auto-builds domain taxonomy on first call using heuristic classification. Use to understan
- `get_edge_bottlenecks`
- `get_endpoint_analytics`: Per-route analytics: request count, error rate, latency, caller services. Requires OTLP trace ingestion. Read-only, queries external runtime data. Use to unders
- `get_federation_impact`
- `get_file_health_timeline`
- `get_graph_timeline`
- `get_health_trends`: Time-series health metrics for a file or module: bug score, complexity, coupling, churn over time. Populated by predict_bugs runs. Use to track if a module is i
- `get_implementations`: Find all classes that implement or extend a given interface or base class. Use when you know the interface name. For full hierarchy tree (ancestors + descendant
- `get_import_graph`: Show file-level dependency graph: what a file imports and what imports it (requires reindex for ESM edge resolution). Use to understand module dependencies for 
- `get_index_health`: Get index status, statistics, health, and pipeline progress (indexing, summarization, embedding). Includes the session projectRoot; when the index is empty, nex
- `get_pagerank`: File importance ranking via PageRank on the import graph. Shows most central/important files. Use to identify architecturally critical files. For combined healt
- `get_plugin_registry`: List registered indexer plugins and edge types. Read-only. Returns JSON: { language_plugins, framework_plugins, edge_type_categories, active_frameworks }; inclu
- `get_project_health`: Structural health: coupling instability, dependency cycles, PageRank rankings, refactor candidates. Use for architecture review as a single aggregated report. F
- `get_refactor_candidates`: Find functions with high complexity called from many files — candidates for extraction to shared modules. Use during architecture review to identify hotspots wo
- `get_runtime_call_graph`: Actual call graph from runtime traces (vs static analysis). Shows observed call paths with call counts and latency. Requires OTLP trace ingestion. Read-only, qu
- `get_runtime_deps`: Which external services (databases, caches, APIs, queues) does this code actually call at runtime. Based on OTLP traces. Read-only, queries external runtime dat
- `get_runtime_profile`: Runtime profile for a symbol or route: call count, latency percentiles (p50/p95/p99), error rate, calls per hour. Requires OTLP trace ingestion. Read-only, quer
- `get_service_deps`: Get external service dependencies: which services this one calls (outgoing) and which call it (incoming). Use to understand a single service's dependency profil
- `get_service_map`: Get map of all services, their APIs, and inter-service dependencies. Auto-detects services from Docker Compose or treats each repo as a service. Use to understa
- `get_subproject_clients`: Find all client calls across subprojects that call a specific endpoint. Shows file, line, call type, and confidence. Use to find all consumers of an endpoint be
- `get_subproject_graph`: Show all subprojects and their cross-repo connections. A subproject is any working repository in your project ecosystem (microservices, frontends, backends, sha
- `get_subproject_impact`: Cross-repo impact analysis: find all client code across subprojects that would break if an endpoint changes. Resolves down to symbol level when per-repo indexes
- `get_symbol_complexity_trend`: Single symbol complexity over git history: cyclomatic, nesting, params, lines at past commits. Requires git. Use to track a specific function's complexity evolu
- `get_symbol_owners`: Git blame-based symbol ownership: who wrote which lines of a specific symbol. Requires git. Use for fine-grained ownership of a specific function/class. For fil
- `get_tech_debt`: Per-module tech debt score (A–F grade) combining: complexity, coupling instability, test coverage gaps, and git churn. Includes actionable recommendations. Use 
- `get_type_hierarchy`: Walk TypeScript class/interface hierarchy: ancestors (what it extends/implements) and descendants (what extends/implements it). Use to understand inheritance tr
- `get_untested_symbols`
- `get_workspace_map`: List all detected monorepo workspaces with file counts, symbol counts, and languages. Returns dependency graph between workspaces showing cross-workspace import
- `graph_query`
- `list_graph_snapshots`: List previously captured graph snapshots, most recent first. Each entry includes its summary so you can inspect counts without diffing. Read-only. Returns JSON:
- `list_pins`: List all active ranking pins with weight, scope, target, expiry, and creator. Use to inspect what is currently boosted/demoted in PageRank-driven ranking. Read-
- `name`: description
- `pin`: Boost (or demote) a symbol and/or file in PageRank-driven ranking by setting a multiplicative weight. Unifies pin_symbol/pin_file — pass symbol_id and/or file_p
- `predict_bugs`
- `query_by_intent`: Map a business question to domain taxonomy → returns domain ownership and relevance scores (no source code). Use when you need to know WHICH DOMAIN owns specifi
- `register_edit`: Notify trace-mcp that a file was edited. Reindexes the single file and invalidates search caches. Call after Edit/Write to keep index fresh — much lighter than 
- `reindex`
- `repair_index`: Apply a targeted repair to the local SQLite index. Modes: drop-orphans (delete embedding rows whose symbol_id no longer exists), drop-vec (drop the entire vecto
- `review_change`: AI-powered review of a file change — identify issues, risks, and suggestions
- `search`: Search code
- `search_text`
- `self_audit`: Dead code & coverage audit: dead exports, untested public symbols, heritage debt. Use as a one-shot health check combining dead exports + untested symbols + her
- `snapshot_graph`: Capture the current graph shape (file/symbol counts, edges by type, top in-degree files, communities, exported symbols) under a named label. Use as a checkpoint
- `subproject_add_repo`
- `subproject_sync`: Re-scan all subprojects: re-discover services, re-parse contracts, re-scan client calls, and re-link everything. Mutates the topology store; idempotent. Use aft
- `suggest_tests`: Suggest test cases for a symbol using AI
- `traverse_graph`: Walk the dependency graph from a starting symbol or file using BFS/DFS, with a hard token budget on the response. Use when you want a structured "what reaches t
- `unpin`: Remove a ranking pin by target. Pass either symbol_id (for a pinned symbol) or file_path (for a pinned file). At least one is required. Returns JSON: { ok, dele
- `verify_index`
- `visualize_graph`: Open interactive HTML graph in browser showing file/symbol dependencies. Supports force/hierarchical/radial layouts, community coloring. Use granularity=symbol 
- `visualize_subproject_topology`: Open interactive HTML visualization of the subproject topology: services as nodes, API calls as edges, health/risk indicators per service. Node size = endpoint 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.