OpenVAS-MCP (CyberSecAuto-Labs/OpenVAS-MCP) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Limited view
71/100
2 months ago

OpenVAS-MCP

Self-hosted MCP server that gives AI agents structured access to OpenVAS vulnerability scanning without sending data externally.

→ CyberSecAuto-Labs/OpenVAS-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

CyberSecAuto-Labs

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
✅
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 1 credential: GVM_PASSWORD
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.
configGVM_PORT
configLOG_LEVEL
configMCP_TRANSPORTstdio stdio, sse, or streamable-http
configMCP_PORT
configGVM_SCAN_POLL_TIMEOUT
configGVM_REPORT_MAX_RESULTS
configGVM_SOCKET_PATH/run/gvmd/gvmd.sock Unix socket path (default connection)
configGVM_HOSTMCP_API_KEYS="supersecrettoken:my-agent" =192.168.1.10 GVM_PASSWORD=secret docker compose up
configGVM_TLSPlain TCP connections (GVM_HOST set, unset) send GVM credentials unencrypted. Use GVM_TLS=1 or a Unix socket for anything beyond local dev.
configGVM_TLS_CAFILE
configGVM_TLS_NO_VERIFY
configGVM_USERNAME
🔐 secretGVM_PASSWORD"env": { "": "secret" } // ← edit this to your GVM password
configMCP_HOST
configMCP_API_KEYS"supersecrettoken:my-agent" GVM_PASSWORD=secret docker compose up
configMCP_POLICY_FILE
configMCP_ALLOW_UNAUTHENTICATEDMCP_API_KEYS is a comma-separated list of token:name pairs sent as a Bearer token by the MCP client. Multiple clients: "tok1:agent1,tok2:agent2". Pass =1 instead to skip auth on a trusted network.
// 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

6/6 tools missing one or more hints — list_targets (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_target (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_tasks (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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

4/6 tool handlers declare input schemas (67%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

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/cybersecauto-labs-openvas-mcp-ynqjx2)](https://m8ven.ai/mcp/cybersecauto-labs-openvas-mcp-ynqjx2)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: e68facb0ef45cee6206b7b1a689f373cf01427ba
code hash: 9e0c114331f1d78bb9b3ed1ddf448587a8967d1ff6de5a1398ac820a96119e1b
verified: 6/18/2026, 10:54:30 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