cortex-mcp (lidless-labs/cortex-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
Emerging
74/100
2 months ago

cortex-mcp

Analysts click through a dozen Cortex jobs by hand. cortex-mcp detonates the indicator and hands your agent one aggregated verdict. Destructive actions stay confirm-gated.

→ lidless-labs/cortex-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

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

lidless-labs

Source: Glama · also listed on github_code

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

GlamaGitHub

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 2 credentials: CORTEX_API_KEY, CORTEX_SUPERADMIN_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.
configCORTEX_ALLOW_DESTRUCTIVENo 0 Set to 1 (or true) to permit running responders (cortex_run_responder), which cause real-world side effects. Off by default. Responders also require confirm=true per call.
🔐 secretCORTEX_API_KEYYes - API key for normal operations (org admin level)
configCORTEX_FILE_BASE_DIRcortex_run_analyzer_file Submit a file to an analyzer. filePath is confined to (disabled if unset); or pass fileBase64
configCORTEX_MAX_FANOUTNo 10 Maximum number of analyzers cortex_analyze_observable will submit to in a single call when fanning out.
🔐 secretCORTEX_SUPERADMIN_KEYNo - Superadmin API key for org/user/definition management
configCORTEX_TIMEOUTNo 30 Request timeout in seconds
configCORTEX_URLYes - Cortex base URL (e.g., http://cortex.example.com:9001)
configCORTEX_VERIFY_SSLNo true Set to false to skip SSL verification. Applied via a scoped HTTP dispatcher for Cortex requests only; it does not disable TLS verification process-wide.
// 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

31/31 tools missing one or more hints — cortex_list_analyzer_definitions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cortex_enable_analyzer (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cortex_disable_analyzer (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +28 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

18/31 tool handlers declare input schemas (58%)

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

Tool test coverage

13/31 tools referenced in tests (42%)

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/solomonneas-cortex-mcp-utsbqz)](https://m8ven.ai/mcp/solomonneas-cortex-mcp-utsbqz)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: a8e707d58b260c976eff562aade655f060347da4
code hash: f968d052161898587650000119e0648a57052935496a68fb04f49c99b8e38e56
verified: 6/12/2026, 11:27:54 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