EVE ESI LLM Bridge (4i7/eve-esi-llm-bridge) is an MCP server listed on the M8ven Trust Index. It scores 54 out of 100, grade D. It declares 9 tools. No publisher has claimed this listing.

D
Caution
54/100
2 days ago

EVE ESI LLM Bridge

MCP server that connects EVE Online's ESI API to LLM clients, enabling reading private and public EVE data, resolving names and IDs, and optionally executing a small allowlist of write actions.

Caution. Specific findings reduced this grade. They are listed on the page. 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

4i7

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 →

Install from

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

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical, 14 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: MCP_AUTH_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical14 high7 medium8 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalnext@16.0.0GHSA-9qr9-h5gf-34mp

Next.js is vulnerable to RCE in React flight protocol

highnext@16.0.0GHSA-267c-6grr-h53f

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes

highnext@16.0.0GHSA-26hh-7cqf-hhc6

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up

highnext@16.0.0GHSA-36qx-fr4f-26g5

Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

highnext@16.0.0GHSA-492v-c6pp-mqqv

Next.js has a Middleware / Proxy bypass through dynamic route parameter injection

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configEVE_ALLOWED_CHARACTER_IDSyour character ID>
configEVE_CLIENT_IDyour own EVE app client ID>
configEVE_ENABLE_WRITE_ACTIONSWrites are off by default. =false ships as the default.
configEVE_ESI_SCOPESspace-separated scopes enabled on your EVE app>
configEVE_USER_AGENT
configMAX_ESI_PAGES
🔐 secretMCP_AUTH_SECRETNo database required for the reference deployment. OAuth transaction state, dynamic client registration metadata, MCP tokens and action tickets are sealed with AES-256-GCM using your own .
configMCP_REFRESH_TTL_DAYS
configPUBLIC_BASE_URL
// quality suggestions

All four hints declared on every tool

9/9 tools missing one or more hints — eve_status (missing: openWorldHint); eve_private_get (missing: idempotentHint, openWorldHint); eve_public_get (missing: idempotentHint, openWorldHint), +6 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 0/9 tools referenced in tests (0%)

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

Secrets not logged

1 secret value sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

1 critical, 14 high severity in production deps — next@16.0.0 (critical), next@16.0.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

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 Verified](https://m8ven.ai/badge/mcp/4i7-eve-esi-llm-bridge-1dv57u?variant=verified)](https://m8ven.ai/mcp/4i7-eve-esi-llm-bridge-1dv57u)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 2b66a19faf653dc6cbee143386e46a9d19a7c1b5
code hash: 4b867b666363615a4716fa83064261f0f23db4e1caed3a356d3fa68d120a0025
verified: 8/23/2026, 4:07:12 AM
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