Nevent MCP (nevent-dev/mcp-nevent) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
2 months ago

Nevent MCP

Enables natural language interaction with Nevent's live-event marketing platform, including campaigns, analytics, paid ads, segments, and short URLs, via 52 tools across 9 categories.

→ nevent-dev/mcp-nevent· listed on glama

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

nevent-dev

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

Glama

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

// key findings
🚨
Known vulnerabilities in dependencies: 2 critical
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: MCP_JWT_SECRET, NEVENT_JWT_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical

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

criticalvitest@2.1.8GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

criticalvitest@2.1.8GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

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.
configGIT_COMMIT_SHA
configLOG_LEVEL
configMCP_ALLOWED_ORIGINS
🔐 secretMCP_JWT_SECRET
configMCP_PORT
configMCP_SERVER_URL
configMCP_TRANSPORT
configNEVENT_API_URL
configNEVENT_DATA_API_URL
🔐 secretNEVENT_JWT_TOKENRequired env: . Optional: NEVENT_OPERATION_MODE (READ_ONLY STANDARD FULL).
configNEVENT_OPERATION_MODERequired env: NEVENT_JWT_TOKEN. Optional: (READ_ONLY STANDARD FULL).
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployMONGODB_URI
// quality suggestions

Tool annotations

35/55 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

55/55 tools missing one or more hints — nevent_analytics_query (missing: idempotentHint); nevent_analytics_capabilities (missing: idempotentHint); nevent_analytics_table_schema (missing: idempotentHint), +52 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

Only 0/55 tool handlers declare input schemas (0%)

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

Tool handlers catch errors

54/55 tool handlers wrap calls in try/catch (98%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

40/55 tools referenced in tests (73%)

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

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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 6 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/nevent-dev-mcp-nevent-qv5dir)](https://m8ven.ai/mcp/nevent-dev-mcp-nevent-qv5dir)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 0f46756646ac39fc80d47eba7c357792b97a7042
code hash: d80eb89520b517f98dd915f8bd90029de517eb991d481f4bdd00a29141ee142b
verified: 6/22/2026, 12:38:14 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