Security Detections MCP (MHaggis/Security-Detections-MCP) is an MCP server listed on the M8ven Trust Index. It scores 77 out of 100, grade B. It declares 25 tools. No publisher has claimed this listing.

B
Caution
77/100
2 months ago

Security Detections MCP

Enables querying and analysis of a unified database of security detection rules across multiple formats, including Sigma, Splunk, Elastic, KQL, and CrowdStrike CQL.

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

MHaggis

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 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 6 credentials: ANTHROPIC_API_KEY, ATTACK_RANGE_PASSWORD, ATTACK_RANGE_PRIVATE_KEY, ENCRYPTION_KEY, OPENROUTER_API_KEY, TURNSTILE_SECRET_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 high1 low

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

high@modelcontextprotocol/sdk@1.25.3GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

lowyaml@2.4.0GHSA-48c2-rrv3-qjmp

yaml is vulnerable to Stack Overflow via deeply nested YAML collections

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.
🔐 secretANTHROPIC_API_KEY
configATTACK_RANGE_IP_WHITELIST
configATTACK_RANGE_KEY_NAME
🔐 secretATTACK_RANGE_PASSWORD
🔐 secretATTACK_RANGE_PRIVATE_KEY
configATTACK_STIX_PATHPath to enterprise-attack.json for threat actor data (optional)
configAWS_REGION
configCQL_HUB_PATHSCQL Hub (CrowdStrike) query directories
configDETECTIONS_DB_PATH
configDRY_RUN
configELASTIC_PATHSElastic detection rule directories
🔐 secretENCRYPTION_KEY
configJAMF_PROTECT_PATHSJamf Protect custom analytic detection directories (macOS)
configKQL_PATHSKQL hunting query directories
🔐 secretOPENROUTER_API_KEY
configSIEM_PLATFORM
configSIGMA_PATHSAfter install, configure env vars (, SPLUNK_PATHS, etc.) to point at your detection repos. See the [Setup Guide](./SETUP.md) for full details.
configSLACK_WEBHOOK_URL
configSPLUNK_MCP_ENABLED
configSPLUNK_PATHSAfter install, configure env vars (SIGMA_PATHS, , etc.) to point at your detection repos. See the [Setup Guide](./SETUP.md) for full details.
configSTORY_PATHSSplunk analytic story directories (optional)
configSUBLIME_PATHSSublime Security rule directories
configSYNC_SOURCE_TYPE
🔐 secretTURNSTILE_SECRET_KEY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_APP_URL
deployNEXT_PUBLIC_SUPABASE_ANON_KEY
deployNEXT_PUBLIC_SUPABASE_URL
deployNEXT_PUBLIC_TURNSTILE_SITE_KEY
deploySUPABASE_SERVICE_ROLE_KEY
// quality suggestions

All four hints declared on every tool

25/25 tools missing one or more hints — search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_by_id (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_raw_yaml (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +22 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

21/25 tool handlers declare input schemas (84%)

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

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 1/25 tools referenced in tests (4%)

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

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.

Shell command execution

128 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.25.3 (high), yaml@2.4.0 (low)

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

Dependency freshness

1/4 production deps stale: @iarna/toml@2023-07-15 (2.9y)

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 7 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/mhaggis/security-detections-mcp?variant=verified)](https://m8ven.ai/mcp/mhaggis/security-detections-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 54a588cad9cae3026279716a6dc8b75af43a4d0a
code hash: a0f016964b6c81a1a2330010aa6ea65db1e6c014251030cc559e427ab1f4c6bc
verified: 6/24/2026, 10:20:05 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