soc-siem-mcp (JoaquinHernandez/soc-siem-mcp-) 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
9 days ago

soc-siem-mcp

Unified SIEM MCP gateway for AI-driven SOC operations and threat hunting across Azure Sentinel, Splunk, Wazuh, IBM QRadar, and Securonix.

→ JoaquinHernandez/soc-siem-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

JoaquinHernandez

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 6 credentials: VIRUSTOTAL_API_KEY, SENTINEL_CLIENT_SECRET, SPLUNK_TOKEN, WAZUH_PASSWORD, QRADAR_SEC_TOKEN, SECURONIX_API_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.
configMCP_TRANSPORTRun the server in SSE mode (=sse on port 8000).
configMCP_PORT
configMCP_HOST
🔐 secretVIRUSTOTAL_API_KEY
configSENTINEL_WORKSPACE_ID
configSENTINEL_TENANT_ID
configSENTINEL_CLIENT_ID
🔐 secretSENTINEL_CLIENT_SECRET
configSPLUNK_HOST
configSPLUNK_PORT
🔐 secretSPLUNK_TOKEN
configSPLUNK_VERIFY_SSL
configWAZUH_API_HOST
configWAZUH_API_PORT
configWAZUH_USER
🔐 secretWAZUH_PASSWORD
configWAZUH_VERIFY_SSL
configQRADAR_HOST
🔐 secretQRADAR_SEC_TOKEN
configQRADAR_VERIFY_SSL
configSECURONIX_HOST
🔐 secretSECURONIX_API_TOKEN
// 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

3/3 tools missing one or more hints — hunt_ioc_across_all_siems (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); enrich_and_attribute_actor (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); hunt_mitre_technique (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

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 3 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/joaquinhernandez-soc-siem-mcp-1qd109)](https://m8ven.ai/mcp/joaquinhernandez-soc-siem-mcp-1qd109)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: f74e5e2078136521fe04e7a0bb416c193df5f881
code hash: f31bacd9026520bae13e9493ac5e947b338120e22de041decc8cfeae8eb9e583
verified: 8/17/2026, 7:36:37 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