LeashIndex Get the report

Index / devtools

Coolify MCP

io-github-frndchagas-coolify-mcp declares 65 capabilities across 65 tools, with 2 critical issues.

99/100 exposureHigh exposure

Manifest recorded 2026-10-21 from tools/list answered by the npm package @fndchagas/coolify-mcp@2.3.1 (published to npm as @fndchagas/coolify-mcp, listed in the official MCP registry as io.github.frndchagas/coolify-mcp 2.3.1), run in an isolated container with no network access and placeholder credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 65 tools

65 of 65 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 14 of 65 tools

14 tools are classified as irreversible and declare no limit.

high · no-expiry · All 65 tools

65 of 65 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 65 tools

65 of 65 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 22 of 65 tools

22 tools can modify data and declare no limit.

low · uncapped-read · 29 of 65 tools

29 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
listResourcesread declared
listProjectsread declared
createProjectwrite inferred
listServersread declared
getServerread declared
listEnvironmentsread declared
createEnvironmentwrite inferred
updateProjectwrite inferred
deleteProjectdestructive declared
createServerwrite inferred
validateServerread declared
listPrivateKeysread declared
createPrivateKeywrite inferred
listGithubAppsread declared
listApplicationsread declared
listDatabasesread declared
listDeploymentsread declared
listAppDeploymentsread declared
getApplicationread declared
getDatabaseread declared
getDeploymentread declared
getLogsread declared
applicationEnvswrite assumed
deploywrite inferred
cancelDeploymentdestructive declared
createApplicationwrite inferred
updateApplicationwrite inferred
deleteApplicationdestructive declared
startApplicationwrite assumed
stopApplicationdestructive declared
restartApplicationdestructive declared
listServicesread declared
createServicewrite inferred
createDatabasewrite inferred
updateDatabasewrite inferred
deleteDatabasedestructive declared
controlDatabasedestructive declared
databaseBackupswrite assumed
databaseEnvswrite assumed
getServiceread declared
updateServicewrite inferred
deleteServicedestructive declared
controlServicedestructive declared
serviceEnvswrite assumed
storageswrite assumed
scheduledTaskswrite assumed
teamsread declared
deletePreviewdestructive declared
updateServerwrite inferred
deleteServerdestructive declared
getServerResourcesread declared
getServerDomainsread declared
getPrivateKeyread declared
updatePrivateKeywrite inferred
deletePrivateKeydestructive declared
getGithubAppRepositoriesread declared
getGithubAppBranchesread declared
diagnoseServerread declared
diagnoseAppread declared
searchDocsread declared
getInfrastructureOverviewread declared
getHealthread declared
restartProjectAppsdestructive declared
redeployProjectwrite assumed
stopAllApplicationsdestructive declared
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.