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

Back to MCP Trust IndexM8ven
C
Emerging
74/100
23 days ago

cveasy-mcp

Provides MCP clients like Claude with tools to query and manage security scans, CVEs, assets, findings, threat intel, and generate polished reports by acting as a lightweight adapter over the CVEasy backend API.

→ CVEasy/cveasy-mcp· 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

⚡ 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

CVEasy

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
✅
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 3 credentials: CVEASY_ACCESS_TOKEN, CVEASY_HTTP_AUTH_TOKEN, CVEASY_SESSION_TOKEN
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.
🔐 secretCVEASY_ACCESS_TOKENAccess token, only needed if the backend runs in production/deployment mode (sent as x-access-token).
configCVEASY_ALLOWED_HOSTS127.0.0.1,localhost,::1 Egress allowlist. The server refuses to start pointed at any other host, because it injects your tokens into every request. Use to disable (not recommended).
configCVEASY_ALLOWED_PATH_ROOTSreport dir, ~/Downloads, ~/Documents Roots that saved reports and system_open_file paths must resolve inside.
configCVEASY_AUDIT_LOGPath for the JSONL tool-call audit log. Unset = stderr.
configCVEASY_BASE_URL"env": { "": "http://127.0.0.1:3001" }
configCVEASY_HTTP_ALLOWED_HOSTSbind host + loopback Comma-separated Host header values accepted. Set this when binding a public hostname.
configCVEASY_HTTP_ALLOWED_ORIGINSComma-separated browser Origins allowed (DNS-rebinding defense). Unset = all browser Origins are refused (403); native clients send no Origin and are unaffected.
🔐 secretCVEASY_HTTP_AUTH_TOKENWhen set, every request must send Authorization: Bearer <token>. Required before exposing a non-loopback bind.
configCVEASY_HTTP_HOST127.0.0.1 HTTP bind address. Loopback by default; set a routable host only behind auth.
configCVEASY_HTTP_PATH/mcp Path serving the MCP endpoint. GET /health is always available for liveness.
configCVEASY_PINNED_MANIFESTOperator-approved tool-manifest digest (get it from tool_manifest).
configCVEASY_PIN_MODEenforce On pin mismatch: enforce withholds mutating tools, warn reports only, off disables the check.
configCVEASY_REPORT_DIR$HOME/Downloads Where report_generate saves files by default.
🔐 secretCVEASY_SESSION_TOKENOperator session token, only needed if RBAC is enabled on the backend (sent as x-session-token).
configCVEASY_TENANTDefault workspace slug, sent as X-Tenant-Id. Prefer passing tenant per call for client work.
configCVEASY_TRANSPORTstdio stdio (local, default) or http (stateless Streamable HTTP — see Remote / HTTP transport below).
configCVEASY_TRIS_AUTHORITYderived Overrides the resolved score authority. Normally leave unset: the authority is contextualized when a workspace is in scope and unresolved otherwise. See Which number is "TRIS"? below.
// 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

61/61 tools missing one or more hints — cve_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cve_get (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cve_top_risk (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +58 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

43/61 tool handlers declare input schemas (70%)

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

Tool test coverage

27/61 tools referenced in tests (44%)

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/cveasy/cveasy-mcp)](https://m8ven.ai/mcp/cveasy/cveasy-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6956cf65fcf0e6fd611529e84b028ad91ed13dec
code hash: 00cafa0254a10bd3d3f1be3a2eb95ff7617a4b9617a4c3a78596dd42a45a7cfa
verified: 8/21/2026, 1:04:26 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