agentic_engineering (kev-wes/agentic_engineering) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 63 tools. No publisher has claimed this listing.

C
Emerging
74/100
7 days ago

agentic_engineering

Building production-grade multi-agent AI systems across OpenAI Agents SDK, CrewAI, LangGraph, AutoGen, and MCP. Personal projects include a deployed career chatbot, autonomous research pipeline, 4-agent coding team, and a multi-LLM trading floor.

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

kev-wes

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 →

Install from

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

// key findings
🚨
Secret credentials may flow to a network call
5 flows detected: PUSHOVER_TOKEN, ANTHROPIC_API_KEY, EXCHANGE_RATE_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 14 credentials: PUSHOVER_TOKEN, GOOGLE_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY, DEEPSEEK_API_KEY, SENDGRID_API_KEY, OLLAMA_API_KEY, CEREBRAS_API_KEY, SERPER_API_KEY, BRAVE_API_KEY, POLYGON_API_KEY, NEWS_API_KEY, EXCHANGE_RATE_API_KEY, MASSIVE_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.
🔐 secretPUSHOVER_TOKEN
configPUSHOVER_USER
🔐 secretGOOGLE_API_KEY
🔐 secretANTHROPIC_API_KEY
configDISCORD_WEBHOOK_URL
configOPENAI_BASE_URL
🔐 secretOPENAI_API_KEY
configANTHROPIC_BASE_URL
🔐 secretDEEPSEEK_API_KEY
configBOT_SELF_NAME
🔐 secretSENDGRID_API_KEY
configPROJECT_ENV_PATH
configGOOGLE_CALENDAR_ID
configGRADIO_ANALYTICS_ENABLED
🔐 secretOLLAMA_API_KEY
🔐 secretCEREBRAS_API_KEY
configUSE_MANY_MODELS
🔐 secretSERPER_API_KEY
configUSE_DYNAMIC_WORKFLOW
configRATELIMIT_API
configRATELIMIT_PASS_TK
configCREWAI_STORAGE_DIR
🔐 secretBRAVE_API_KEY
🔐 secretPOLYGON_API_KEY
🔐 secretNEWS_API_KEY
🔐 secretEXCHANGE_RATE_API_KEY
🔐 secretMASSIVE_API_KEY
configMCP_MAX_RETRIES
configMCP_RETRY_DELAY
configPOLYGON_PLAN
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

2/63 tools have annotations

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

All four hints declared on every tool

62/63 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), +59 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 test coverage

Only 8/63 tools referenced in tests (13%)

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

Secrets not logged

5 secret values sent to print/logger.info

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 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/kev-wes/agentic_engineering)](https://m8ven.ai/mcp/kev-wes/agentic_engineering)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 552671987c8dbafd083b860e05c0fccf49a4444b
code hash: aa6c5e2890f39cfe5b8e639333faea78f7206a98f447ce16d7d65cec42d2b7ac
verified: 9/3/2026, 7:37: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