alibabacloud-rds-openapi-mcp-server (aliyun/alibabacloud-rds-openapi-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 57 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Emerging
89/100
7 days ago

alibabacloud-rds-openapi-mcp-server

A server that provides management and connectivity for Alibaba Cloud RDS database services via OpenAPI, enabling users to create, query, and modify RDS instances through MCP integration.

→ aliyun/alibabacloud-rds-openapi-mcp-server· listed on pulsemcp

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

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

aliyun

Source: PulseMCP · also listed on modelscope, mcp.so

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

PulseMCPmodelscopemcp.so

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

// key findings
✅
57 tools verified — handlers match their declared behaviour
26 read-only tools verified — handlers contain no write/delete/exec
✅
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 8 credentials: API_KEY, ALIBABA_CLOUD_ACCESS_KEY_SECRET, ALIBABA_CLOUD_SECURITY_TOKEN, DINGTALK_APP_CLIENT_SECRET, FEISHU_APP_SECRET, QQ_CLIENT_SECRET, WECOM_SECRET, ACCESS_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.
configSERVER_PORT
configSERVER_TRANSPORT
configMCP_TOOLSETSEnvironment variable:
configSERVER_HOST
🔐 secretAPI_KEYWhen is configured, MCP clients must send Authorization: Bearer <API_KEY>.
configRDS_BOT_BRIDGES
configTOOLSET_DEBUG
configALIBABA_CLOUD_ACCESS_KEY_ID
🔐 secretALIBABA_CLOUD_ACCESS_KEY_SECRET
🔐 secretALIBABA_CLOUD_SECURITY_TOKEN
configDINGTALK_APP_CLIENT_ID
🔐 secretDINGTALK_APP_CLIENT_SECRET
configDINGTALK_ROBOT_CODE
configFEISHU_BOT_OPEN_ID
configFEISHU_BOT_USER_ID
configFEISHU_BOT_NAME
configFEISHU_GROUP_POLICY
configFEISHU_APP_ID
🔐 secretFEISHU_APP_SECRET
configFEISHU_DOMAIN
configQQ_APP_ID
🔐 secretQQ_CLIENT_SECRET
configWECOM_BOT_ID
🔐 secretWECOM_SECRET
configWECOM_WEBSOCKET_URL
configRDS_COPILOT_CHAT_WORKERS
configRDS_COPILOT_ENDPOINT
configACCESS_KEY_ID
🔐 secretACCESS_SECRET
configALLOW_HEADER_CREDENTIALS
// quality suggestions

Tool annotations

26/57 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

57/57 tools missing one or more hints — describe_db_instances (missing: destructiveHint, idempotentHint, openWorldHint); describe_db_instance_attribute (missing: destructiveHint, idempotentHint, openWorldHint); describe_db_instance_performance (missing: destructiveHint, idempotentHint, openWorldHint), +54 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

30/57 tools referenced in tests (53%)

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/aliyun/alibabacloud-rds-openapi-mcp-server)](https://m8ven.ai/mcp/aliyun/alibabacloud-rds-openapi-mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 3311bd91c675093a3416d64e3d859d474e6b5983
code hash: 13a48fba848affd78b373daa04ab41feb2d297fcd77c8dd5518c5480ea9a0737
verified: 9/3/2026, 9:11:14 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