Back to MCP Trust Indexm8ven
C
Limited view
73/100
14 days ago

hack-setup

→ sumitmalik51/hack-setup· listed on github_code

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

sumitmalik51

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

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 4 credentials: AZURE_CLIENT_SECRET, CLIENT_SECRET, AZURE_OPENAI_KEY, SCHEDULER_ALLOW_LEGACY_INLINE_SECRET
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.
configCHATBOT_ENABLE_MUTATION_TOOLSThe AI assistant is read-only by default. Mutation tools are hidden/blocked unless =true, and tool responses redact passwords, TAPs, secrets, and tokens.
configAZURE_TENANT_ID
configAZURE_CLIENT_ID
🔐 secretAZURE_CLIENT_SECRET... # OR cert auth below
configTENANT_ID
configCLIENT_ID
🔐 secretCLIENT_SECRET
configSCHEDULER_CLIENT_SECRET_ENVFor durable scheduled jobs without adding resources, set an App Service/local environment variable and reference it with , for example:
configSCHEDULER_CLIENT_SECRET_URIIf you already have Key Vault, you can optionally use an existing secret URI via ; the app will resolve it at runtime with managed identity. This is optional and does not create a new Key Vault.
configSCHEDULER_CONNECTION_ID
configAZURE_OPENAI_ENDPOINT
🔐 secretAZURE_OPENAI_KEY
configAZURE_OPENAI_DEPLOYMENT
configEXTRACT_ROOT
configEXTRACT_SERVICE_TIMEOUT
configEXTRACT_PREFETCH_TIMEOUT
configGITHUB_EXTRACT_PAT
configGITHUB_EXTRACT_ORG
configRBAC_SCAN_CONCURRENCY
configAUTO_COST_TEAMS_INTERVAL_SECONDS
configAUTO_COST_TEAMS_MODE
configTEAMS_COST_WEBHOOK_URL
configPOWER_AUTOMATE_COST_WEBHOOK_URL
configLIFECYCLE_TEAMS_WEBHOOK_URL
configTEAMS_WEBHOOK_URL
configLIFECYCLE_POWER_AUTOMATE_URL
configPOWER_AUTOMATE_WEBHOOK_URL
🔐 secretSCHEDULER_ALLOW_LEGACY_INLINE_SECRET
configPLATFORM_CONFIG_FILE
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployAZURE_STORAGE_CONNECTION_STRING
// 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 — _call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); provision_onedrive (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); upload_folder (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.

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/sumitmalik51-hack-setup-138iwd)](https://m8ven.ai/mcp/sumitmalik51-hack-setup-138iwd)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 196a5f55dcf5d58cc2cd06c73c30f28300485ad7
code hash: 2e6df2ad2704a69a7ed98f1c8564624eb7e85ae7eac83b3244235b0c635c0436
verified: 8/8/2026, 8:28:24 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