Emerging

74/100

1 day ago

Axolotl

Item: Axolotl
Rating: 74
Author: M8ven

Axolotl is a self-healing software engineering agent that monitors GitLab CI/CD pipelines and automatically responds to failures. It analyzes build logs, identifies root causes, generates fixes, creates a branch, and raises a merge request for human approval.

→ VipulMore11/Axolotl · listed on github_code

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 push why connect →

Who stands behind it

VipulMore11

Source: github_code

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

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

// key findings

🚨

Secret credentials may flow to a network call

1 flow detected: WEBHOOK_SECRET. We can’t prove the destination matches the brand the credential belongs to.

🔐

You'll be asked for 5 credentials: GEMINI_API_KEY, WEBHOOK_SECRET, BITBUCKET_CLIENT_SECRET, GITLAB_CLIENT_SECRET, JWT_SECRET

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// 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.

🔐 secretGEMINI_API_KEYyour_gemini_api_key_here

configGEMINI_MODELgemini-2.5-flash

🔐 secretWEBHOOK_SECRETaxolotl-webhook-secret

configBITBUCKET_REDIRECT_URI

configGITLAB_REDIRECT_URICopy the generated HTTPS URL (e.g. https://abc123.ngrok-free.app) and update in backend/.env.

configWEBHOOK_SERVER_HOST

configWEBHOOK_SERVER_PORT

configBITBUCKET_CLIENT_ID

🔐 secretBITBUCKET_CLIENT_SECRET

configFRONTEND_URL

configGITLAB_CLIENT_IDyour_gitlab_oauth_client_id

🔐 secretGITLAB_CLIENT_SECRETyour_gitlab_oauth_client_secret

configGITLAB_BASE_URL

🔐 secretJWT_SECRET

configMONGODB_DB_NAME

Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.

deployNEXT_PUBLIC_API_URL

deployNEXT_PUBLIC_WS_URL

deployMONGODB_CONNECTION_STRING

// 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

8/8 tools missing one or more hints — get_pipeline_logs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_branch (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); update_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not logged

4 secret values sent to console.log

Redact or omit secret values from log output.

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 5 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/vipulmore11-axolotl-108ml7)](https://m8ven.ai/mcp/vipulmore11-axolotl-108ml7)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: da126eb387e8e6892c2b78f7c8f31b45b91ff3a2

code hash: 4464cfa769dd2bc08b6b7062612ce88a549d42ee249372942d9f0781857190ea

verified: 8/18/2026, 7:05:53 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