a2e-engine (MauricioPerera/a2e-engine) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 12 tools. The publisher has proved control of what we score (Verified Publisher). It is connected through the M8ven GitHub App, so the listing is re-checked on every push.

B
Emerging
89/100
2 hours ago

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

⚡ Live Monitored

Monitored 0 days · every push re-verified

Who stands behind it

gmail.com (@MauricioPerera) · Verified Publisher

Source: github_app_install

Maintenance & responsiveness
as of 2026-08-20
Issues closed (90d): 0 · 0 open
Releases (90d): none
Active contributors (6mo): 2

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// 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.
🔐
You'll be asked for 2 credentials: A2E_API_KEY, A2E_MCP_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
Are you the publisher? Confirm or correct these findings.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configA2E_API_BASEproduct-api base URL (default http://localhost:8080).
🔐 secretA2E_API_KEYif set, sent as X-API-Key (only needed when the product-api
🔐 secretA2E_MCP_TOKEN
configMCP_BIND
configMCP_PORT
// 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

12/12 tools missing one or more hints — retrieve_catalog (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_piece (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_connections (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 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.

Tests exist

No test files found

Add tests that exercise each declared tool.

Domain consistency

npm scope @a2e doesn't match GitHub owner mauricioperera

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/mauricioperera/a2e-engine)](https://m8ven.ai/mcp/mauricioperera/a2e-engine)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6048724fe7e8b7a734865d81affa28a841193b1f
code hash: b75f5d65d4702fef54fa453568fede314b27ba27bc91bf1bd2d36a8205a135dc
verified: 9/10/2026, 3:46:24 PM
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