MCP-Sentinel (RoshiniMlakshmana/MCP-vulnerability-detection) is an MCP server listed on the M8ven Trust Index. It scores 0 out of 100, grade F. It declares 5 tools. No publisher has claimed this listing.

F
Warning
0/100
1 month ago

MCP-Sentinel

A safety guard for AI assistants that inspects actions (file reads, queries, etc.) and classifies them as SAFE, SUSPICIOUS, or BLOCK with explanations, using both known-attack patterns and behavior-based zero-day detection.

Warning. Serious findings were identified. Review the full report before connecting. 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

RoshiniMlakshmana

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

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.

⏳ This MCP is queued for scoring. Check back in a few minutes.
// key findings
🚨
Reads files from sensitive locations
Touches: ~/.config/Claude/claude_desktop_config.json
🔐
You'll be asked for 2 credentials: OPENAI_API_KEY, THREATFOX_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.
configBASELINE_PATH
configNO_COLOR
configMODEL_PROVIDER
🔐 secretOPENAI_API_KEYUsing OpenAI: copy .env.example to .env and paste your into it.
configOLLAMA_URL
configOLLAMA_CHAT_MODEL
configOPENAI_CHAT_MODEL
configCHROMA_PATH
configCOLLECTION
configQUARANTINE_PATH
configSTATE_PATH
configMAX_AGE_DAYS
configATLAS_URL
configOPEN_IOC_FEED_META_URL
configTHREATFOX_API_URL
🔐 secretTHREATFOX_API_KEY
configEMBEDDING_PROVIDERFree, on your own computer: install [Ollama](https://ollama.com), then in a file called .env set =ollama.
configOLLAMA_EMBEDDING_MODEL
configOPENAI_EMBEDDING_MODEL
configPENDING_REMEDIATIONS_PATH
configFLOW_ID
configNOTIFY_ON3. Fully quit and reopen Claude Desktop. Now you can ask Claude to check any action, and you'll get a desktop pop-up if something's dangerous (turn alerts on with =block,suspicious).
// 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

5/5 tools missing one or more hints — scan_tool_call (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); explain_verdict (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); approve_remediation (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +2 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

4/5 tool handlers declare input schemas (80%)

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

Tool handlers catch errors

3/5 tool handlers wrap calls in try/catch (60%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

No access to sensitive paths

Reads sensitive paths: ~/.config/Claude/claude_desktop_config.json

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

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 6 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/roshinimlakshmana/mcp-vulnerability-detection?variant=verified)](https://m8ven.ai/mcp/roshinimlakshmana/mcp-vulnerability-detection)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 2ffbf6b8b6c6ab6876dc9a43975c0b4c58e3aa20
code hash: 92fd9744f2726a0333dba2bf81846766faef5d306da0585d55f3595fbf930e1d
verified: 7/16/2026, 8:41:36 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