Neo MCP (NeoAIResearch/neo-mcp) is an MCP server listed on the M8ven Trust Index. It scores 69 out of 100, grade C. It declares 30 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
69/100

Neo MCP

Integrates an autonomous AI engineering agent into your editor via the Model Context Protocol, allowing you to describe AI/ML tasks in plain English and execute them locally.

→ NeoAIResearch/neo-mcp· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

NeoAIResearch

Source: Glama

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

Glamanot scored here

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
✅
30 tools verified — handlers match their declared behaviour
5 read-only tools verified — handlers contain no write/delete/exec
✅
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: NEO_BYOK_KEY, NEO_SECRET_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.
🔐 secretNEO_BYOK_KEY
configNEO_BYOK_MODEL
configNEO_BYOK_PROVIDER
configNEO_DEPLOYMENT_IDNo Pin a specific daemon UUID (auto-generated by default)
configNEO_DEPLOYMENT_ID_MODE
configNEO_HOME
🔐 secretNEO_SECRET_KEYe =sk-v1-YOUR_KEY \
configNEO_SUPPRESS_CONSOLE
configNEO_TASK_TIMEOUT_HOURS
configNEO_THREAD_WORKSPACES_MAX
configNEO_THREAD_WORKSPACES_TTL_SECONDS
configNEO_WORKSPACE_DIRNo Override workspace directory (useful in Docker or CI)
configNEO_WORKSPACE_REGISTRATION_WAIT_SECONDS
configNEO_TRACE_ROUTING
configNEO_ENVIRONMENT
configNEO_ENV
configNEO_API_URL
configNEO_INTEGRATIONS_BACKEND
configNEO_AUTH_URL
configNEO_RELAY_URL
configNEO_PUBLIC_URL
configNEO_HEALTH_PORT
configCOMSPEC
configSHELL
// quality suggestions

Tool annotations

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

4/30 tools missing one or more hints — neo_submit_task (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); neo_get_messages (missing: openWorldHint); neo_add_integration (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 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

11/13 tool handlers declare input schemas (85%)

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

Tool test coverage

Only 0/30 tools referenced in tests (0%)

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 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/neoairesearch/neo-mcp)](https://m8ven.ai/mcp/neoairesearch/neo-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ffa481d849a5b62853c7c0fe8b008af192822da1
code hash: 2f114be7f1f11303bf4b1b86c7e296da7cf02a1f023a8619d85ec80cee5423d8
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