ast-impact-mapper-mcp (vola-trebla/ast-impact-mapper-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 15 tools. No publisher has claimed this listing.

C
Emerging
74/100

ast-impact-mapper-mcp

MCP server that analyzes TypeScript/JavaScript codebases via AST parsing and dependency graph tracing to identify affected tests, detect dead code, circular dependencies, and trace import chains, enabling AI agents to run only relevant tests.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

vola-trebla

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// tools this server exposes15 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

get_affected_tests
explain_impact
get_affected_tests_by_branch
get_dependency_graph
get_coverage_gaps
get_test_summary
identify_unreachable_modules
detect_architectural_cycles
differentiate_type_impact
analyze_api_surface_mutation
get_rename_aware_diff
refresh_project
get_symbol_dependency_graph

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

generate_skeleton_view

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

generate_test_command

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

// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

15/15 tools missing one or more hints — get_affected_tests (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); explain_impact (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_affected_tests_by_branch (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

12/15 tool handlers declare input schemas (80%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool test coverage

Only 0/15 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/vola-trebla/ast-impact-mapper-mcp)](https://m8ven.ai/mcp/vola-trebla/ast-impact-mapper-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: f895ef288b8b06a46dde1de6f21a0bcd228b9643
code hash: fc0e522f516c3277ab4809927017175846465902c1779063e6209b38ee21b927
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client