Sentinel MCP Server (pranjal-lnct/Scurity-MCP-Server) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 10 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
71/100

Sentinel MCP Server

Sentinel is an enterprise-grade security server that integrates tools like Semgrep, Trivy, and Gitleaks via Docker to perform automated vulnerability scanning and compliance checks. It enables users to conduct static analysis, secret detection, and AI-powered threat modeling directly through Model Context Protocol-compatible IDEs.

→ pranjal-lnct/Scurity-MCP-Server· 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

pranjal-lnct

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

Glamanot scored here

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 1 credential: SENTINEL_LLM_API_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.
configSENTINEL_SEMGREP_IMAGECustom Docker image for Semgrep returntocorp/semgrep
configSENTINEL_TRIVY_IMAGECustom Docker image for Trivy aquasec/trivy
configSENTINEL_GRYPE_IMAGECustom Docker image for Grype anchore/grype
configSENTINEL_GITLEAKS_IMAGE
configSENTINEL_ZAP_IMAGE
configSENTINEL_CLAMAV_IMAGE
configSENTINEL_TESTSSL_IMAGECustom Docker image for testssl.sh drwetter/testssl.sh
configSENTINEL_SCHEMATHESIS_IMAGECustom Docker image for Schemathesis schemathesis/schemathesis:stable
configSENTINEL_LOG_LEVEL"": "INFO"
configSENTINEL_DOCKER_TIMEOUTTimeout for Docker commands in seconds 600
🔐 secretSENTINEL_LLM_API_KEYAPI Key for AI Threat Modeling (e.g., OpenAI) None (Falls back to heuristic)
configSENTINEL_LLM_MODELLLM Model to use gpt-4o
configSENTINEL_LLM_API_BASE
// 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

10/10 tools missing one or more hints — run_sast_scan (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); run_sca_scan (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); run_secret_scan (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 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.

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 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/pranjal-lnct/scurity-mcp-server)](https://m8ven.ai/mcp/pranjal-lnct/scurity-mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 31beb72a396fc62592628f93578f99fed60fe37e
code hash: 5dcddd020fbd8eaff3bf3b4ecab3d7e5f96db8b5425de8488d761f75dc28f1ee
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