ai-engineer-agentic-track (alej4ndro-cm/ai-engineer-agentic-track) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 139 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
7 days ago

ai-engineer-agentic-track

→ alej4ndro-cm/ai-engineer-agentic-track· 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 pushwhy connect →

Who stands behind it

alej4ndro-cm

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
11 flows detected: PUSHOVER_TOKEN, ANTHROPIC_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 12 credentials: OPENAI_API_KEY, SERPER_API_KEY, PUSHOVER_TOKEN, GOOGLE_API_KEY, OPENROUTER_API_KEY, GROQ_API_KEY, ANTHROPIC_API_KEY, PUSHOVER_USER_KEY, GEMINI_API_KEY, DEEPSEEK_API_KEY, SENDGRID_API_KEY, RESEND_API_KEY
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.
configREPORT_STORAGE_DIR
🔐 secretOPENAI_API_KEY
🔐 secretSERPER_API_KEY
🔐 secretPUSHOVER_TOKEN
configPUSHOVER_USER
🔐 secretGOOGLE_API_KEY
configOPENAI_MODEL
🔐 secretOPENROUTER_API_KEY
configOPENROUTER_BASE_URL
configMODEL
configSECRET_PHARSE
🔐 secretGROQ_API_KEY
configPROFILE_DIR
configAGENT_NAME
configOPENROUTER_MODEL
configOPENROUTER_SITE_URL
configOPENROUTER_APP_NAME
🔐 secretANTHROPIC_API_KEY
configDISCORD_WEBHOOK_URL
🔐 secretPUSHOVER_USER_KEY
configOPENAI_BASE_URL
configANTHROPIC_BASE_URL
🔐 secretGEMINI_API_KEY
🔐 secretDEEPSEEK_API_KEY
configOPEN_ROUTER
configBOT_SELF_NAME
🔐 secretSENDGRID_API_KEY
configPROJECT_ENV_PATH
🔐 secretRESEND_API_KEY
configRESEND_TO_EMAIL
configDEEP_RESEARCH_QUERY
configSENDGRID_FROM_EMAIL
configSENDGRID_TO_EMAIL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

139/139 tools missing one or more hints — current_date (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); current_time (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); shift_date (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +136 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

130/139 tool handlers declare input schemas (94%)

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

Tool test coverage

Only 10/139 tools referenced in tests (7%)

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

Secrets not logged

3 secret values sent to print

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/alej4ndro-cm/ai-engineer-agentic-track)](https://m8ven.ai/mcp/alej4ndro-cm/ai-engineer-agentic-track)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 85f2645c63c99b92d14391e559a43a3966918f99
code hash: 832b078b8ed71bc014a67ae23e6745c3ccdd9f3b94251e97893114717f4ee567
verified: 9/3/2026, 6:24:45 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