CloudHostAI
REMOTE · CLOUDHOSTAI.ELITEAIEMPIRE.COM
Managed deployments on your own Hetzner servers.
Available components
Last scanned (14 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Cloud Infrastructure
Recent critical change
Authorization (17 Nov 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cloudhosting_destroy_server). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1046 tokens (~55/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety90
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 3 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cloudhosting_list_deploys" implies "deploy" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +45
- Authorization: unverified → fail ▼ critical
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Tool “get_checkout_link” rewrote its description, which is the text the model reads security
- Tool “get_company_info” rewrote its description, which is the text the model reads security
- Tool “search_site” rewrote its description, which is the text the model reads security
- Schema quality: 47 → 55 ▼ functional
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.27 ▲ functional
- “get_checkout_link” added an optional parameter “accept_terms” cosmetic
- “get_checkout_link” added an optional parameter “buyer_email” cosmetic
- “get_checkout_link” added an optional parameter “store_handle” cosmetic
- “search_site” reworded the description of “query” cosmetic
- “search_site” dropped the optional parameter “limit” cosmetic
- Tool “get_company_info” changed its title: Company info cosmetic
- Tool “search_site” changed its title: Search this site cosmetic
- 16 Nov 26 −44
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 −2
- HSTS header: pass → fail ▼ security
- Schema quality: 740 → 895 ▼ functional
- New tool “get_checkout_link” functional
- New tool “get_company_info” functional
- New tool “list_pricing” functional
- New tool “search_site” functional
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://cloudhostai.eliteaiempire.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=eliteaiempire.com | CN=YE1,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 517249ed134f0bde704a0af855a2b2bb62e |
| SANs: *.eliteaiempire.com, eliteaiempire.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cloudhostai.eliteaiempire.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| eliteaiempire.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cloudhostai.eliteaiempire.com/mcp | Verified | 200 | |
| http (plaintext) | http://cloudhostai.eliteaiempire.com/mcp | HTTPS enforced | 302 | https://cloudhostai.eliteaiempire.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cloudhosting_create_project ~81
Register a project (repo + server size). Creates no server. [scope: write]
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | – |
| custom_domain | string | – | – |
| location | string | – | – |
| name | string | yes | – |
| repo_url | string | yes | Public Git https URL with a Dockerfile. |
| server_type | string | – | – |
No output schema declared.
No examples provided.
cloudhosting_delete_project ~65
DESTRUCTIVE: delete a project record (server must be destroyed first). Requires confirm=true. [scope: write]
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true. Acknowledges the action. |
| project_id | integer | yes | Project id from cloudhosting_list_projects. |
No output schema declared.
No examples provided.
cloudhosting_deploy_project ~73
Deploy (creates or redeploys the server in YOUR Hetzner account; Hetzner bills you). Requires confirm=true. [scope: write]
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true. Acknowledges the action. |
| project_id | integer | yes | Project id from cloudhosting_list_projects. |
No output schema declared.
No examples provided.
cloudhosting_destroy_server ~65
DESTRUCTIVE: delete the project server from your Hetzner account. Requires confirm=true. [scope: write]
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true. Acknowledges the action. |
| project_id | integer | yes | Project id from cloudhosting_list_projects. |
No output schema declared.
No examples provided.
cloudhosting_export ~33
Export all your objects (json, or csv of projects). [scope: read]
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
No output schema declared.
No examples provided.
cloudhosting_get_account ~25
Plan, project limit and usage of the account. [scope: billing]
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cloudhosting_get_hetzner_status ~32
Whether your Hetzner token is connected (never returns it). [scope: read]
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cloudhosting_get_logs ~40
Fetch container logs over SSH from the project server. [scope: read]
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | Project id from cloudhosting_list_projects. |
No output schema declared.
No examples provided.
cloudhosting_get_pricing ~20
Public plan prices and the agent API quota.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cloudhosting_get_project ~34
Get one project. [scope: read]
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | Project id from cloudhosting_list_projects. |
No output schema declared.
No examples provided.
cloudhosting_get_project_status ~42
Refresh and return the server status from Hetzner. [scope: read]
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | Project id from cloudhosting_list_projects. |
No output schema declared.
No examples provided.
cloudhosting_get_usage ~26
API/MCP calls this month against the free quota. [scope: read]
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cloudhosting_list_deploys ~42
Deploy history for a project (last 20). [scope: read]
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | Project id from cloudhosting_list_projects. |
No output schema declared.
No examples provided.
cloudhosting_list_projects ~19
List your projects. [scope: read]
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cloudhosting_preview_deploy ~89
Dry run: check a public repo + branch and show what a deploy would create. Public, no key, creates nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Defaults to the repo default branch. |
| location | string | – | – |
| repo_url | string | yes | https://github.com/owner/repo (also gitlab.com, bitbucket.org) |
| server_type | string | – | – |
No output schema declared.
No examples provided.
get_checkout_link Checkout link ~206
Checkout URL for a plan. With no arguments: the main paid plan. Where the site supports it the URL is a Stripe-hosted Checkout session (created unpaid; a human pays, nothing is charged by this tool). A free plan is only returned when the plan is requested or the company sells nothing else.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_terms | boolean | – | ONLY where the site requires the buyer to accept its Terms/refund policy before checkout: set true only after the human buyer has read and accepted the policy links the tool lists. Never set it on yo… |
| buyer_email | string | – | only for sites that need the buyer's email or store handle before checkout: the human buyer's own receipt email |
| interval | string | – | – |
| plan | string | – | plan name from list_pricing |
| store_handle | string | – | only where the site asks for it (StoreForge): the store handle the buyer chose, 3+ chars a-z 0-9 - |
No output schema declared.
No examples provided.
get_company_info ~29
Who runs CloudHostAI, what it does, contact and legal links. Public, no key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_pricing Pricing ~34
Current plans and prices in USD: plan, interval, amount_usd, currency, what_you_get. No account needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_site ~37
Keyword search over the public pages of cloudhostai.eliteaiempire.com. Public, no key.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the CloudHostAI MCP server?
CloudHostAI is a hosted endpoint at https://cloudhostai.eliteaiempire.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · cloudhostai.eliteaiempire.com
claude mcp add --transport http com-eliteaiempire-cloudhostai 'https://cloudhostai.eliteaiempire.com/mcp'
What is the CloudHostAI MCP server?
CloudHostAI is an MCP server listed in the public MCP registry as com.eliteaiempire/cloudhostai. Managed deployments on your own Hetzner servers. This page covers its hosted endpoint (https://cloudhostai.eliteaiempire.com/mcp).
Is the CloudHostAI MCP server safe to use?
CloudHostAI scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CloudHostAI MCP server expose?
CloudHostAI exposes 19 tools: cloudhosting_list_projects, cloudhosting_get_project, cloudhosting_get_project_status, cloudhosting_list_deploys, cloudhosting_get_logs, and 14 more. Their descriptions and schemas cost roughly 992 tokens of context every time the server is loaded.
Does the CloudHostAI MCP server require authentication?
No. We connected to CloudHostAI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CloudHostAI MCP server still maintained?
CloudHostAI is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the CloudHostAI MCP server?
VerifyMCP ran 13 checks on CloudHostAI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.