Data_Mining_Oxygent (Mao-Xiaoxi/Data_Mining_Oxygent) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Caution
73/100
3 days ago

Data_Mining_Oxygent

数据挖掘期末项目

Caution. Specific findings reduced this grade. They are listed on the page. 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

Mao-Xiaoxi

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: OPENAI_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 4 credentials: JD_ERP_PASSWORD, DEFAULT_LLM_API_KEY, OPENAI_API_KEY, ES_TEST_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.
configK8S_MCP_TRANSPORT
configK8S_MCP_PORT
configK8S_MCP_TOOLSETS
configKUBECONFIG
configJD_ERP_USERNAME
🔐 secretJD_ERP_PASSWORD
configK8S_MCP_READ_ONLY
configK8S_MCP_DISABLE_DESTRUCTIVE
🔐 secretDEFAULT_LLM_API_KEY
configDEFAULT_LLM_BASE_URL
configDEFAULT_LLM_MODEL_NAME
configOPENAI_BASE_URL
🔐 secretOPENAI_API_KEY
configOPENAI_MODEL_NAME
configSQL_TOOLS_DB_URL
configAPP_ENV
configES_HOST_LIST
configES_TEST_USER
🔐 secretES_TEST_PASSWORD
// 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

119/119 tools missing one or more hints — mcp (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); power (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); basemcpclient (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +116 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.

Destructive tools are labelled

3 tools perform destructive updates without destructiveHint — text_to_speech deletes at line 1047 (os.unlink(temp_file.name)); new_delete_file deletes at line 36 (os.remove(path)); delete_file deletes at line 42 (os.remove(path))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

107/115 tool handlers declare input schemas (93%)

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

Tool test coverage

38/119 tools referenced in tests (32%)

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

Secrets stay with their owner

1 secret sent to a request target we could not resolve (OPENAI_API_KEY → dynamic) — often a configured endpoint, not necessarily third-party

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

Secrets not logged

4 secret values sent to print

Redact or omit secret values from log output.

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 7 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/mao-xiaoxi-data-mining-oxygent-1chhk6?variant=verified)](https://m8ven.ai/mcp/mao-xiaoxi-data-mining-oxygent-1chhk6)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 4b9ffc6f81012a1815bece112315adb472a7791b
code hash: d1e0c759132c20266cddcecb027087c29ff23ec45089a4ac2c22eca35a205ede
verified: 9/3/2026, 6:21:11 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