Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions
Directory / CloudHostAI
CloudHostAI
by cloudhostai.eliteaiempire.com · https://cloudhostai.eliteaiempire.com/mcp
Managed deployments on your own Hetzner servers.
11 of 11 checks · 9 Nov 2026
At a glance
- Runs where
- On their server. What you send to it goes to them.
- What you need
- Nothing: it answered without a login
- Tools
- 15 tools
- Its own safety labels
- 11 read-only, 2 labeled as deleting or destroying, 2 labeled as changing things
- Memory it takes
- About 1,500 tokens of your AI's memory, just for its tool descriptions
- Largest answer
- About 1.2 KB in our test
- Tools that look alike
- 2 pairs of tools with nearly the same description, so the AI may pick the wrong one
- Speed
- Average answer in our test: 147 ms
Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 9 Nov 2026.
Is CloudHostAI MCP server safe?
- None of the hidden-instruction wordings we know were found in its 15 tool descriptions.
- Its error messages showed no secrets or internal details.
- 11 of its 15 tools are labeled read-only; the others may change or send things.
- Overall it scored 88/100 on 9 Nov 2026.
A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.
What this test does not check
- Its source code and packages.
- What a tool quietly does behind the scenes, such as writing a file or calling another service.
- Instructions hidden inside live tool answers. We only look for those in tool descriptions.
- Hidden instructions worded in a way our list doesn't know yet.
- Tools that could change something. Those are read, never run.
What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection
Known security advisories
It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.
What it can do
15 tools, in the server's own words.
cloudhosting_list_projectsread-onlyList your projects.
cloudhosting_get_projectread-onlyGet one project.
cloudhosting_get_project_statusread-onlyRefresh and return the server status from Hetzner.
cloudhosting_list_deploysread-onlyDeploy history for a project (last 20).
cloudhosting_get_logsread-onlyFetch container logs over SSH from the project server.
cloudhosting_get_hetzner_statusread-onlyWhether your Hetzner token is connected (never returns it).
cloudhosting_get_usageread-onlyAPI/MCP calls this month against the free quota.
cloudhosting_exportread-onlyExport all your objects (json, or csv of projects).
cloudhosting_get_accountread-onlyPlan, project limit and usage of the account.
cloudhosting_create_projectRegister a project (repo + server size).
cloudhosting_deploy_projectDeploy (creates or redeploys the server in YOUR Hetzner account; Hetzner bills you).
cloudhosting_destroy_serverDESTRUCTIVE: delete the project server from your Hetzner account.
cloudhosting_delete_projectDESTRUCTIVE: delete a project record (server must be destroyed first).
cloudhosting_preview_deployread-onlyDry run: check a public repo + branch and show what a deploy would create.
cloudhosting_get_pricingread-onlyPublic plan prices and the agent API quota.
Test results
Safe mode: only tools labeled read-only were run. How the test works
- !Ready for the newest MCP versionnote
1 warning
- !Uses an older MCP version (2025-03-26). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
- !Every tool is describednote
5 warnings
- !cloudhosting_export: Inputs with no description: format
- !cloudhosting_create_project: Inputs with no description: branch, custom_domain, location, name, server_type
- !cloudhosting_preview_deploy: Inputs with no description: location, server_type
- !cloudhosting_list_projects and cloudhosting_get_project have nearly the same description (60% of their words are shared; the only difference: "list" vs "get"), so an AI may not know which to pick
- !cloudhosting_destroy_server and cloudhosting_delete_project have nearly the same description (60% of their words are shared; the only difference: "hetzner", "account" vs "record", "must", "destroyed"), so an AI may not know which to pick
- !Follows MCP best practices (not scored yet)note
2 tips (not scored)
- !4 tools not labeled read-only don't say whether running them twice is safe (idempotentHint): cloudhosting_create_project, cloudhosting_deploy_project, cloudhosting_destroy_server, cloudhosting_delete_project
- !1 tool answers with structured data but doesn't declare its shape (outputSchema): cloudhosting_get_pricing. If those answers change shape, nothing can catch it; with a schema, every answer is checked.
- ✓ConnectsConnected in 897 mspass
- ✓Lists its toolsFound 15 toolspass
- ✓Tools are labeled safe or dangerousEvery tool has a safety labelpass
- ✓No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.pass
- ✓Tools work with good inputspass
All good
- –cloudhosting_list_projects: Needs you to sign in, so it was not tested (not counted against the server)
- –cloudhosting_get_project: Needs you to sign in, so it was not tested (not counted against the server)
- –cloudhosting_get_project_status: Needs you to sign in, so it was not tested (not counted against the server)
- –cloudhosting_list_deploys: Needs you to sign in, so it was not tested (not counted against the server)
- –cloudhosting_get_logs: Needs you to sign in, so it was not tested (not counted against the server)
- –cloudhosting_get_hetzner_status: Needs you to sign in, so it was not tested (not counted against the server)
- –cloudhosting_get_usage: Needs you to sign in, so it was not tested (not counted against the server)
- –cloudhosting_export: Needs you to sign in, so it was not tested (not counted against the server)
- and 7 more
- ✓Bad inputs give a clean errorpass
All good
- –cloudhosting_get_project: Needs you to sign in, so bad inputs were not tested
- –cloudhosting_get_project_status: Needs you to sign in, so bad inputs were not tested
- –cloudhosting_list_deploys: Needs you to sign in, so bad inputs were not tested
- –cloudhosting_get_logs: Needs you to sign in, so bad inputs were not tested
- –cloudhosting_export: Needs you to sign in, so bad inputs were not tested
- ✓cloudhosting_preview_deploy: Refused missing required input "repo_url" with a clear error
- ✓cloudhosting_preview_deploy: Refused wrong type for "repo_url" with a clear error
- ✓Fast enoughpass
All good
- ✓Connecting took 897 ms
- ✓Listing tools took 169 ms
- ✓Average tool answer: 147 ms
- ✓cloudhosting_preview_deploy: Slowest tool: cloudhosting_preview_deploy (165 ms)
- ✓No secrets leakedChecked 21 error messages: no secrets or internal detailspass
- –Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)not tested
Test it yourself
Free and open source. Same checks, same score.
npx qamcp-cli https://cloudhostai.eliteaiempire.com/mcpShow this score on GitHub
Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.
[](https://qamcp.dev/s/com-eliteaiempire-cloudhostai.html)Score over time
- 9 Nov 202688
One test so far. New tests will show here.
Reviews
Coming soon: reviews from people who use CloudHostAI, signed in with GitHub, one per person. Reviews never change the score.
QAmcp Monitor tests it every hour and emails you when it goes down, the score drops, a tool changes or a secret leaks. Free for 1 server, no card.
Have a concern, or want it removed? Ask us and we'll take it off the list. How the directory works