supber_project (TheCong2004/supber_project) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 5 tools. No publisher has claimed this listing.

Emerging

74/100

9 days ago

supber_project

Item: supber_project
Rating: 74
Author: M8ven

→ TheCong2004/supber_project · listed on github_code

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

TheCong2004

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

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.

✅

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 3 credentials: SECRETKEY_AWS_ACCESS_KEY, SECRETKEY_AWS_SECRET_KEY, EMAIL_PASSWORD

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.

configADMIN_RATE_LIMIT_MESSAGE

configAPP_URL

configBLOB_STORAGE_PATH

configCLOUD_FREE_ID

configCLOUD_PRO_ID

configCLOUD_STARTER_ID

configCONVERSATION_TTL_HOURS

configDENYLIST_URLS

configFLOWISE_FILE_SIZE_LIMIT

configFLOWISE_SECRETKEY_OVERWRITE

configHOST

configLIBREFANG_CONFIG

configLIBREFANG_DEFAULT_AGENT

configLIBREFANG_DISPATCH_LOG

configLIBREFANG_ECHO_TRACKER

configLIBREFANG_LID_PERSIST

configLIBREFANG_OWNER_CHANNEL

configLIBREFANG_SILENT_V2

configLIBREFANG_URL

configMCP_CORS_ORIGINS

configMETRICS_PROVIDER

configMODE

🔐 secretSECRETKEY_AWS_ACCESS_KEY

configSECRETKEY_AWS_AUTH_PREFIX

configSECRETKEY_AWS_NAME

configSECRETKEY_AWS_REGION

🔐 secretSECRETKEY_AWS_SECRET_KEY

configSECRETKEY_PATH

configSECRETKEY_STORAGE_TYPE

configTRUST_PROXY

configWA_HEALTH_STALE_MS

configWA_HEARTBEAT_CHECK_MS

configWA_HEARTBEAT_MS

configWHATSAPP_DB_PATH

configWHATSAPP_GATEWAY_PORT

configWHATSAPP_OWNER_JID

configBASE_SHA

configHEAD_SHA

configIMAP_SERVER

configIMAP_PORT

🔐 secretEMAIL_PASSWORD

configEMAIL_USERNAME

configLIBREFANG_AGENT_ID

configLIBREFANG_MESSAGE

Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.

deployNEXT_PUBLIC_LIBREFANG_AUTH_BYPASS

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

5/5 tools missing one or more hints — dynamodb_kv_store (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dynamodb_kv_retrieve (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); agentflow_tool (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 test coverage

3/5 tools referenced in tests (60%)

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

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/thecong2004/supber_project)](https://m8ven.ai/mcp/thecong2004/supber_project)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: a28cf35f4c8f2e725bd43420c95bfd9432d9e5bb

code hash: 836dd11792352c2b3456cd086476574a2d7ac249211ea6c04c10ab18912c955a

verified: 9/3/2026, 5:10:43 PM

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