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.…
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
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 publishedThis tool published no description. Forge does not invent one.
explain_impactNo description publishedThis tool published no description. Forge does not invent one.
get_affected_tests_by_branchNo description publishedThis tool published no description. Forge does not invent one.
get_dependency_graphNo description publishedThis tool published no description. Forge does not invent one.
get_coverage_gapsNo description publishedThis tool published no description. Forge does not invent one.
get_test_summaryNo description publishedThis tool published no description. Forge does not invent one.
identify_unreachable_modulesNo description publishedThis tool published no description. Forge does not invent one.
detect_architectural_cyclesNo description publishedThis tool published no description. Forge does not invent one.
differentiate_type_impactNo description publishedThis tool published no description. Forge does not invent one.
analyze_api_surface_mutationNo description publishedThis tool published no description. Forge does not invent one.
get_rename_aware_diffNo description publishedThis tool published no description. Forge does not invent one.
refresh_projectNo description publishedThis tool published no description. Forge does not invent one.
get_symbol_dependency_graphNo description publishedThis tool published no description. Forge does not invent one.
generate_skeleton_viewNo description publishedThis tool published no description. Forge does not invent one.
generate_test_commandprivilegedNo description publishedThis 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.
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…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.