EvoHarness (Nagrax/EvoHarness) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 14 tools. The publisher has confirmed an email address for this listing, which proves an inbox rather than ownership (Claimed).

Back to MCP Trust IndexM8ven
C
Emerging
74/100

EvoHarness

自进化 Agent 运行时 · 对大模型只会推理、难以可靠操作真实环境并沉淀可复用经验的局限，构建自进化的Agentic Harness运行时，使Agent能在真实代码任务上自主执行，并随使用持续沉淀能力、自我进化。

→ Nagrax/EvoHarness· listed on github_repo_search

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

Nagrax · Claimed

Source: github_repo_search

⚡ Upgrade to Live Monitored

Connect your repo and M8ven re-verifies it on the push itself. Without it we re-check verified listings about once a day, so a fix can sit unseen. Read-only, one click, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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 4 credentials: APIKEY, EVOHARNESS_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY
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.
🔐 secretAPIKEY
🔐 secretEVOHARNESS_API_KEY
🔐 secretOPENAI_API_KEY
🔐 secretANTHROPIC_API_KEY
configAPIWeb：python -m server.app——FastAPI + SSE 事件桥，agents/ 核心零改动接入；支持访客自带 key（BYOK，key 只存浏览器）
configEVOHARNESS_API_BASE
configOPENAI_BASE_URL
configANTHROPIC_BASE_URL
configMODEL
configEVO_RELOAD
configEVOHARNESS_AUTO_SKILL_EVOLUTION
configEVOHARNESS_AUTO_SKILL_TARGET
configNO_STREAM
configEVOHARNESS_MAX_MEMORY_RECALL
configComSpec
configSHELL
configEVOHARNESS_SKILL_ZOMBIE_DAYS
configEVOHARNESS_SKILL_ZOMBIE_MAX_RETRIEVED
configEVOHARNESS_SKILL_PRUNE_PROJECT
configEVOHARNESS_USAGE_SAMPLE_DAY_LIMIT
configEVOHARNESS_SKILL_USAGE_PRUNE_MIN_RETRIEVED
configEVOHARNESS_SKILL_USAGE_PRUNE_MAX_USED
configALL_PROXY
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

14/14 tools missing one or more hints — read_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); write_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); edit_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +11 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 1/14 tools referenced in tests (7%)

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

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 3 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/nagrax/evoharness)](https://m8ven.ai/mcp/nagrax/evoharness)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 3007ac64e52e1684a647737f871a64383e32e899
code hash: 0e54761e73bcabcb61d0cf7d0d33d7204804433fe0bbd39ff9eb3d8737cfa1a3
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