# io.github.vola-trebla/ast-impact-mapper-mcp (npm · ast-impact-mapper-mcp)

MCP server that uses TypeScript AST to find which tests are affected by a code change

- Trust score: 69/100 (medium)
- Change this week: +23
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `ast-impact-mapper-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/vola-trebla-ast-impact-mapper-mcp/ast-impact-mapper-mcp.md), [page](https://verifymcp.io/servers/vola-trebla-ast-impact-mapper-mcp/ast-impact-mapper-mcp)

## Channel facts

- Registry: `npm`
- Package: `ast-impact-mapper-mcp`
- Version: `0.3.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (104 of 108), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (104 of 108), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 73 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1557 tokens (~103/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add vola-trebla-ast-impact-mapper-mcp -- npx -y ast-impact-mapper-mcp
```

### Codex

```bash
codex mcp add vola-trebla-ast-impact-mapper-mcp -- npx -y ast-impact-mapper-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vola-trebla-ast-impact-mapper-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "ast-impact-mapper-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vola-trebla-ast-impact-mapper-mcp --command npx --arg -y --arg ast-impact-mapper-mcp
```

### Hermes

```yaml
mcp_servers:
  vola-trebla-ast-impact-mapper-mcp:
    command: "npx"
    args: ["-y", "ast-impact-mapper-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "vola-trebla-ast-impact-mapper-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ast-impact-mapper-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-02 (score 66, +45)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: MIT

### 2026-08-01 (score 21, +16)

- [functional improvement] Tool coverage: unverified → 100

### 2026-07-31 (score 5, −41)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (15)

### `get_affected_tests` (~124 tokens)

Given a list of changed source files, returns which test files are affected — directly or transitively through the import graph. Use to answer: which tests should I run after this code change?

Input parameters:

- `changed_files` (array): List of changed file paths (absolute or relative to project_root)
- `git_diff` (string): Raw output of `git diff --name-only` — newline-separated file paths. Use instead of changed_files when piping git output directly.
- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)

### `explain_impact` (~115 tokens)

Finds the exact import chain that connects a changed source file to a test file. Use to answer: why does changing file X cause test Y to be affected? Returns the step-by-step import path from the test to the changed file.

Input parameters:

- `changed_file` (string, required): The source file that was changed (absolute or relative to project_root)
- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)
- `test_file` (string, required): The test file to explain the connection for

### `get_affected_tests_by_branch` (~90 tokens)

Runs `git diff --name-only <base_branch>...HEAD` internally and returns affected test files. Use instead of get_affected_tests when you want the server to handle the git diff automatically.

Input parameters:

- `base_branch` (string): Branch to diff against (default: main)
- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)

### `get_dependency_graph` (~106 tokens)

Returns the direct import graph for a specific file: what it imports, and what imports it. Use to answer: what depends on this file? What does this file depend on?

Input parameters:

- `file_path` (string, required): Path to the file (absolute or relative to project_root)
- `format` (string): Output format — json (default) or mermaid flowchart diagram
- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)

### `get_coverage_gaps` (~111 tokens)

Finds source files that are not reachable from any test file through the import graph — i.e. completely untested code. Use to answer: which parts of the codebase have zero test coverage?

Input parameters:

- `limit` (integer): Max uncovered files to return
- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)
- `source_dirs` (array): Restrict results to these directories (absolute or relative to project_root). Defaults to the entire project.

### `get_test_summary` (~79 tokens)

Returns a bird's-eye view of the project's test structure: coverage rate, most-imported source files (highest risk to change), and tests with the deepest import chains. Use to answer: what is the overall test health of this project?

Input parameters:

- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)

### `identify_unreachable_modules` (~144 tokens)

Finds source files that are never imported by any other file — dead code candidates safe to delete. Automatically excludes known entry points (index.ts, main.ts, pages/, routes/, app/, api/, bin/). Use to answer: which files in this codebase are orphaned and can be safely removed?

Input parameters:

- `entry_points` (array): Additional entry point files to exclude (absolute or relative to project_root). Common patterns like index.ts and pages/ are auto-excluded.
- `limit` (integer): Max unreachable files to return (default: 50)
- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)

### `detect_architectural_cycles` (~77 tokens)

Detects circular import dependencies — A imports B which imports C which imports A. Cycles cause unpredictable module initialization order and indicate tight coupling. Use to answer: are there circular dependencies I need to break before refactoring?

Input parameters:

- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)

### `differentiate_type_impact` (~123 tokens)

Classifies each changed file as type-only or runtime, then splits affected tests into "must run" vs "skippable". A test is skippable when the changed file contains only TypeScript type declarations (interfaces/type aliases) or the test imports it via `import type`. Use to answer: which tests can I skip after a type-only refactor?

Input parameters:

- `changed_files` (array, required): Changed file paths (absolute or relative to project_root)
- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)

### `analyze_api_surface_mutation` (~116 tokens)

Compares a file against its HEAD version and classifies the change as `breaking_api_change` (exported function signature changed, parameter removed/added, interface field removed) or `internal_refactor` (only implementation body changed). Use to answer: is this PR a breaking change or a safe refactor?

Input parameters:

- `file_path` (string, required): Path to the changed file (absolute or relative to project_root)
- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)

### `get_rename_aware_diff` (~128 tokens)

Like get_affected_tests_by_branch, but correctly handles renamed and moved files. Uses --find-renames to detect file moves and --ignore-all-space to skip whitespace-only changes. Use instead of get_affected_tests_by_branch when the branch contains refactors or file moves.

Input parameters:

- `base_branch` (string): Branch to diff against (default: main)
- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)
- `similarity_threshold` (integer): Minimum similarity % to consider a file move a rename (default: 90)

### `refresh_project` (~65 tokens)

Clears the cached AST for a project root, forcing a full re-parse on the next call. Use after switching branches, running git pull, or adding/removing files.

Input parameters:

- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)

### `get_symbol_dependency_graph` (~97 tokens)

Retrieves a bidirectional or directed dependency graph mapped to individual declarations, functions, and variables.

Input parameters:

- `direction` (string): Graph traversal direction
- `file_path` (string, required): Absolute path to the TypeScript source file
- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)
- `symbol_name` (string): Target export symbol. If omitted, maps all symbols in the file

### `generate_skeleton_view` (~106 tokens)

Generates a token-optimized representation of a source file by stripping function and method bodies, keeping only JSDocs and declarations with line numbers.

Input parameters:

- `file_path` (string, required): Absolute path to the target source file
- `include_jsdoc` (boolean): Whether to preserve JSDoc annotations
- `include_private_members` (boolean): Whether to list private/internal symbols
- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)

### `generate_test_command` (~76 tokens)

Outputs the optimal test execution command for Jest, Vitest, or Playwright based on changed files.

Input parameters:

- `changed_files` (array, required): List of modified source file paths
- `project_root` (string, required): Absolute path to the TypeScript project root (must contain tsconfig.json)
- `runner` (string): Test runner to target

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/vola-trebla-ast-impact-mapper-mcp/ast-impact-mapper-mcp#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 66
- 2026-08-01: 21
- 2026-07-31: 5
- 2026-07-30: 46
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/ast-impact-mapper-mcp
- Socket report: https://socket.dev/npm/package/ast-impact-mapper-mcp
- Repository: https://github.com/vola-trebla/ast-impact-mapper-mcp
- Changelog RSS feed: https://verifymcp.io/servers/vola-trebla-ast-impact-mapper-mcp/ast-impact-mapper-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/vola-trebla-ast-impact-mapper-mcp/ast-impact-mapper-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/vola-trebla-ast-impact-mapper-mcp/ast-impact-mapper-mcp