dokploy-mcp-server (sapientsai/dokploy-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 27 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

dokploy-mcp-server

A comprehensive MCP server for Dokploy that provides 14 action-based tools covering the full DevOps lifecycle with minimal token usage. It enables AI assistants to manage projects, applications, databases, domains, servers, and more through a unified interface.

→ sapientsai/dokploy-mcp-server· listed on glama

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 pushwhy connect →

Who stands behind it

sapientsai

Source: Glama · also listed on github_repo_search

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

Glamanot scored hereGitHub

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
🚨
Secret credentials may flow to a network call
1 flow detected: DOKPLOY_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 1 credential: DOKPLOY_API_KEY
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.
🔐 secretDOKPLOY_API_KEYAPI key from Dokploy Settings > API Keys
configDOKPLOY_URLYour Dokploy instance URL
configGITHUB_REF_NAME
configHOSTHTTP host (httpStream mode only)
configLOG_LEVEL
configTRANSPORT_TYPETransport mode: stdio or httpStream
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
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

27/27 tools missing one or more hints — dokploy_server (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dokploy_application (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dokploy_audit_log (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +24 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.

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 2 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/sapientsai/dokploy-mcp-server)](https://m8ven.ai/mcp/sapientsai/dokploy-mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: adca35f88d248e8247d02b286a7b179040a07479
code hash: 285ddfb620d7ea4bc78fbbd06bf3f3d44a240d466c87496772a57cece7cd3b00
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