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

Back to MCP Trust IndexM8ven
C
Limited view
69/100
2 months ago

security-tools

Provides security tools (prompt injection detection, CVE lookup, version impact assessment) for MCP clients like Claude.

→ yeodh10/security-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

yeodh10

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

Glamanot scored hereGitHub

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.
🔐
You'll be asked for 2 credentials: ANTHROPIC_API_KEY, SECURITY_MCP_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.
configSECURITY_MCP_CACHE_DIR
configSECURITY_MCP_LLM_MODEL2차 LLM(기본 claude-opus-4-8, 로 변경 가능)에게 한 번 더 묻습니다.
🔐 secretANTHROPIC_API_KEY가 있고 use_llm=True(기본)면, 룰이 확정 차단(block)하지 못한 입력에 한해
configSECURITY_MCP_LLM_CACHE
configSECURITY_MCP_PORTSECURITY_MCP_HOST=0.0.0.0 =8000 \
configSECURITY_MCP_ALLOWED_HOSTS설정 시 DNS-rebinding 보호 ON. sse도 SECURITY_MCP_TRANSPORT=sse로 선택 가능.
configSECURITY_MCP_TRANSPORTstreamable-http \
🔐 secretSECURITY_MCP_TOKEN$(openssl rand -hex 24) \
configSECURITY_MCP_HOST0.0.0.0 SECURITY_MCP_PORT=8000 \
configSECURITY_MCP_RATE_LIMIT레이트리밋: IP별 고정 윈도우( 기본 120 / SECURITY_MCP_RATE_WINDOW 60초, 0=끔). 초과 → 429.
configSECURITY_MCP_RATE_WINDOW레이트리밋: IP별 고정 윈도우(SECURITY_MCP_RATE_LIMIT 기본 120 / 60초, 0=끔). 초과 → 429.
configSMOKE_PORT
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

4/4 tools missing one or more hints — scan_prompt_injection (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); lookup_cve (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); find_cves_for_product (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 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 handlers catch errors

Only 1/4 tool handlers wrap calls in try/catch (25%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

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

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 5 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/yeodh10/security-mcp)](https://m8ven.ai/mcp/yeodh10/security-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6884d86e3946f8a72a44b46a345d99d835ad12d5
code hash: c841e92ac794df3b226d2cdd01f1ddfc66b77722f1e8ac14872a413331dc3640
verified: 6/18/2026, 10:28:55 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