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

santhosh2005-santhosh2005

Source: 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 →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: OIDC_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🚨
Reads files from sensitive locations
Touches: /.dockerenv
🚨
Code appears obfuscated
1 file are unreadable to a human reviewer. Cannot audit what they do.
🚨
Known vulnerabilities in dependencies: 1 critical, 8 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 4 credentials: ADMIN_PASSWORD, DEMO_ADMIN_PASS, ENCRYPTION_KEY, OIDC_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical8 high21 low

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

criticalvitest@3.2.4GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

highmulter@2.1.1GHSA-72gw-mp4g-v24j

Multer vulnerable to Denial of Service via deeply nested field names

highnodemailer@8.0.5GHSA-p6gq-j5cr-w38f

Nodemailer: Message-level raw option bypasses disableFileAccess/disableUrlAccess, enabling arbitrary file read and full-response SSRF in the delivered message

highundici@7.0.0GHSA-4cwx-7wf7-3272

undici vulnerable to cross-user information disclosure and parse-time crash via degenerate private cache directives

highundici@7.0.0GHSA-f269-vfmq-vjvj

Undici: Malicious WebSocket 64-bit length overflows parser and crashes the client

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.
configADMIN_EMAIL
🔐 secretADMIN_PASSWORD
configALLOWED_ORIGINS
configALLOW_INTERNAL_NETWORK
configAPP_URL
configAPP_VERSION
configCOOKIE_SECURE
configDB_PATH
configDEFAULT_LANGUAGE
configDEMO_ADMIN_EMAIL
🔐 secretDEMO_ADMIN_PASS
configDEMO_ADMIN_USER
configDEMO_MODE
🔐 secretENCRYPTION_KEY
configFORCE_HTTPS
configHOST
configHSTS_INCLUDE_SUBDOMAINS
configLOG_LEVEL
configMCP_MAX_SESSION_PER_USER
configMCP_RATE_LIMIT
configOIDC_ADMIN_CLAIM
configOIDC_ADMIN_VALUE
configOIDC_CLIENT_ID
🔐 secretOIDC_CLIENT_SECRET
configOIDC_DISCOVERY_URL
configOIDC_DISPLAY_NAME
configOIDC_ISSUER
configOIDC_ONLY
configOIDC_SCOPE
configTRUST_PROXY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
deploySMTP_FROM
deploySMTP_HOST
deploySMTP_PASS
deploySMTP_PORT
deploySMTP_SKIP_TLS_VERIFY
deploySMTP_USER
// 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

158/158 tools missing one or more hints — assign_place_to_day (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); unassign_place (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); update_assignment_time (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +155 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

144/158 tool handlers declare input schemas (91%)

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

Tool handlers catch errors

Only 10/158 tool handlers wrap calls in try/catch (6%)

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

README present

No README found

Add a README.md describing the server and its tools.

License file

No license file

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

Tool test coverage

Only 1/158 tools referenced in tests (1%)

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

No access to sensitive paths

Reads sensitive paths: /.dockerenv

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

Shell command execution

324 child_process calls — runs shell commands

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

Readable source code

1 file appear obfuscated

Ship unminified, readable source.

Secrets stay with their owner

1 secret/sensitive value flow into network calls (OIDC_CLIENT_SECRET → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not written to files

2 secret values written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Production dependencies are patched

0 critical, 8 high severity in production deps — multer@2.1.1 (high), nodemailer@8.0.5 (high)

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

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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 14 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/santhosh2005-santhosh2005-odootraveloop1-p2rrzt?variant=verified)](https://m8ven.ai/mcp/santhosh2005-santhosh2005-odootraveloop1-p2rrzt)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 4683f4dc39a50372c15406f1100483dbde5faf68
code hash: badc62bc5d76273cfb65792998210b8154e49fd5df9df9393ecfc6d0d2918c32
verified: 8/8/2026, 7:16:27 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