io.github.vola-trebla/ast-impact-mapper-mcp
NPM · AST-IMPACT-MAPPER-MCP · SCANNED SEP 20
MCP server that uses TypeScript AST to find which tests are affected by a code change
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 121 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1557 tokens (~103/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.vola-trebla/ast-impact-mapper-mcp server?
io.github.vola-trebla/ast-impact-mapper-mcp runs locally as an npm package, launched with npx -y ast-impact-mapper-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ast-impact-mapper-mcp
claude mcp add vola-trebla-ast-impact-mapper-mcp -- npx -y ast-impact-mapper-mcp
{
"mcpServers": {
"vola-trebla-ast-impact-mapper-mcp": {
"command": "npx",
"args": [
"-y",
"ast-impact-mapper-mcp"
]
}
}
} {
"servers": {
"vola-trebla-ast-impact-mapper-mcp": {
"command": "npx",
"args": [
"-y",
"ast-impact-mapper-mcp"
]
}
}
} codex mcp add vola-trebla-ast-impact-mapper-mcp -- npx -y ast-impact-mapper-mcp
{
"$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 mcp add vola-trebla-ast-impact-mapper-mcp --command npx --arg -y --arg ast-impact-mapper-mcp
mcp_servers:
vola-trebla-ast-impact-mapper-mcp:
command: "npx"
args: ["-y", "ast-impact-mapper-mcp"] {
"McpServers": {
"vola-trebla-ast-impact-mapper-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"ast-impact-mapper-mcp"
]
}
}
} assistant mcp add vola-trebla-ast-impact-mapper-mcp -t stdio -c npx -a -y ast-impact-mapper-mcp
{
"mcpServers": {
"vola-trebla-ast-impact-mapper-mcp": {
"command": "npx",
"args": [
"-y",
"ast-impact-mapper-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/ast-impact-mapper-mcp@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 105 packages
| Packages resolved | 105 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_api_surface_mutation ~116
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?
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the changed file (absolute or relative to project_root) |
| project_root | string | yes | Absolute path to the TypeScript project root (must contain tsconfig.json) |
No output schema declared.
No examples provided.
detect_architectural_cycles ~77
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?
| Name | Type | Req | Description |
|---|---|---|---|
| project_root | string | yes | Absolute path to the TypeScript project root (must contain tsconfig.json) |
No output schema declared.
No examples provided.
differentiate_type_impact ~123
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?
| Name | Type | Req | Description |
|---|---|---|---|
| changed_files | array | yes | Changed file paths (absolute or relative to project_root) |
| project_root | string | yes | Absolute path to the TypeScript project root (must contain tsconfig.json) |
No output schema declared.
No examples provided.
explain_impact ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| changed_file | string | yes | The source file that was changed (absolute or relative to project_root) |
| project_root | string | yes | Absolute path to the TypeScript project root (must contain tsconfig.json) |
| test_file | string | yes | The test file to explain the connection for |
No output schema declared.
No examples provided.
generate_skeleton_view ~106
Generates a token-optimized representation of a source file by stripping function and method bodies, keeping only JSDocs and declarations with line numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | 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 | yes | Absolute path to the TypeScript project root (must contain tsconfig.json) |
No output schema declared.
No examples provided.
generate_test_command ~76
Outputs the optimal test execution command for Jest, Vitest, or Playwright based on changed files.
| Name | Type | Req | Description |
|---|---|---|---|
| changed_files | array | yes | List of modified source file paths |
| project_root | string | yes | Absolute path to the TypeScript project root (must contain tsconfig.json) |
| runner | string | – | Test runner to target |
No output schema declared.
No examples provided.
get_affected_tests ~124
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?
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Absolute path to the TypeScript project root (must contain tsconfig.json) |
No output schema declared.
No examples provided.
get_affected_tests_by_branch ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| base_branch | string | – | Branch to diff against (default: main) |
| project_root | string | yes | Absolute path to the TypeScript project root (must contain tsconfig.json) |
No output schema declared.
No examples provided.
get_coverage_gaps ~111
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?
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max uncovered files to return |
| project_root | string | yes | 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. |
No output schema declared.
No examples provided.
get_dependency_graph ~106
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?
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the file (absolute or relative to project_root) |
| format | string | – | Output format — json (default) or mermaid flowchart diagram |
| project_root | string | yes | Absolute path to the TypeScript project root (must contain tsconfig.json) |
No output schema declared.
No examples provided.
get_rename_aware_diff ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| base_branch | string | – | Branch to diff against (default: main) |
| project_root | string | yes | 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) |
No output schema declared.
No examples provided.
get_symbol_dependency_graph ~97
Retrieves a bidirectional or directed dependency graph mapped to individual declarations, functions, and variables.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Graph traversal direction |
| file_path | string | yes | Absolute path to the TypeScript source file |
| project_root | string | yes | 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 |
No output schema declared.
No examples provided.
get_test_summary ~79
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?
| Name | Type | Req | Description |
|---|---|---|---|
| project_root | string | yes | Absolute path to the TypeScript project root (must contain tsconfig.json) |
No output schema declared.
No examples provided.
identify_unreachable_modules ~144
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?
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Absolute path to the TypeScript project root (must contain tsconfig.json) |
No output schema declared.
No examples provided.
refresh_project ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_root | string | yes | Absolute path to the TypeScript project root (must contain tsconfig.json) |
No output schema declared.
No examples provided.
What is the io.github.vola-trebla/ast-impact-mapper-mcp server?
io.github.vola-trebla/ast-impact-mapper-mcp is listed in the public MCP registry as io.github.vola-trebla/ast-impact-mapper-mcp. MCP server that uses TypeScript AST to find which tests are affected by a code change. This page covers its npm package (ast-impact-mapper-mcp).
Is the io.github.vola-trebla/ast-impact-mapper-mcp server safe to use?
io.github.vola-trebla/ast-impact-mapper-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.vola-trebla/ast-impact-mapper-mcp server expose?
io.github.vola-trebla/ast-impact-mapper-mcp exposes 15 tools: get_affected_tests, explain_impact, get_affected_tests_by_branch, get_dependency_graph, get_coverage_gaps, and 10 more. Their descriptions and schemas cost roughly 1,557 tokens of context every time the server is loaded.
Is the io.github.vola-trebla/ast-impact-mapper-mcp server still maintained?
io.github.vola-trebla/ast-impact-mapper-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.vola-trebla/ast-impact-mapper-mcp server under?
io.github.vola-trebla/ast-impact-mapper-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.