Ext Ops Panel
Open dashboard
Comparison

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

mendapi is an MCP server published by mendapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.vola-trebla/ast-impact-mapper-mcp is an MCP server published by vola-trebla. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacemendapiio.github.vola-trebla/ast-impact-mapper-mcp
Official MCP Registry Listed
Version: 0.5.6
Downloads/month (npm): 343
Downloads/week (npm): 30
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.3.1
Downloads/month (npm): 159
Downloads/week (npm): 15
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

mendapi vs io.github.vola-trebla/ast-impact-mapper-mcp
Factmendapiio.github.vola-trebla/ast-impact-mapper-mcp
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mendapi)On your machine (ast-impact-mapper-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/mendapi/mendapigithub.com/vola-trebla/ast-impact-mapper-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

mendapi

In its own words, on Official MCP Registry:

Detect API breaking changes, scan your codebase for impact, and draft the fix. Runs locally.

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

In its own words, on Official MCP Registry:

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

How to run each

mendapi As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mendapi -- npx -y mendapi

io.github.vola-trebla/ast-impact-mapper-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ast-impact-mapper-mcp -- npx -y ast-impact-mapper-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: mendapi · What it can do: io.github.vola-trebla/ast-impact-mapper-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built