io.github.vola-trebla/ast-impact-mapper-mcp

MCPcommunity
v0.3.1io.github.vola-treblaUnknownUpdated 4mo agonpmGitHub

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

An MCP server that uses the TypeScript AST to determine exactly which tests are affected by a code change — so your AI agent stops running the entire suite and starts running only what matters. When you change , which tests should run? Most tools either run everything (slow) or guess by filename (wrong). Import graphs don't lie — if a test transitively imports the changed file, it needs to run.…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4mo agoLast update
Package
Authorio.github.vola-trebla
LicenseUnknown
Version0.3.1
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface15 tools · 1 privileged
Security scan✓ Cleanv0.3.1 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

15 tools · 1 privileged
Statically extracted from the published packagev0.3.1 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_affected_testsNo description published

This tool published no description. Forge does not invent one.

explain_impactNo description published

This tool published no description. Forge does not invent one.

get_affected_tests_by_branchNo description published

This tool published no description. Forge does not invent one.

get_dependency_graphNo description published

This tool published no description. Forge does not invent one.

get_coverage_gapsNo description published

This tool published no description. Forge does not invent one.

get_test_summaryNo description published

This tool published no description. Forge does not invent one.

identify_unreachable_modulesNo description published

This tool published no description. Forge does not invent one.

detect_architectural_cyclesNo description published

This tool published no description. Forge does not invent one.

differentiate_type_impactNo description published

This tool published no description. Forge does not invent one.

analyze_api_surface_mutationNo description published

This tool published no description. Forge does not invent one.

get_rename_aware_diffNo description published

This tool published no description. Forge does not invent one.

refresh_projectNo description published

This tool published no description. Forge does not invent one.

get_symbol_dependency_graphNo description published

This tool published no description. Forge does not invent one.

generate_skeleton_viewNo description published

This tool published no description. Forge does not invent one.

generate_test_commandprivilegedNo description published

This tool published no description. Forge does not invent one.

0 of 15 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

An MCP server that uses the TypeScript AST to determine exactly which tests are affected by a code change — so your AI agent stops running the entire suite and starts running only what matters. When you change , which tests should run? Most tools either run everything (slow) or guess by filename (wrong). Import graphs don't lie — if a test transitively imports the changed file, it needs to run. This server builds a precise dependency graph from your TypeScript project and answers that question…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.