Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Contabo (VPS) MCP Server

REMOTE · CONTABO.RUN.MCP.COM.AI

Contabo API (v1.0.0) as MCP tools for cloud provisioning, and management. Powered by HAPI MCP server

−37 this week 0 Trust /100

Last scanned (2 months ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 6 Aug 2026.

Category Cloud Infrastructure

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety–

Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.

Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool Safety in Tool SafetyNot scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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 →

Changelog

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.

  • 18 Aug 26 −12

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 13 Aug 26 −12

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 12 Aug 26 −13

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Aug 26 −12

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 9 Aug 26 −12

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 7 Aug 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: 0.37 → unverified ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 5 Aug 26 +1

    The score moved with no change recorded against any check. We would rather say so than guess.

Diagnostics

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 18 Aug 2026 · Probed https://contabo.run.mcp.com.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.com.ai CN=WE1,O=Google Trust Services,C=US 11 Aug 2026 9 Nov 2026 ECDSA 256 ECDSA-SHA256 831856af5774d610ebfd6b9fd9b2b74
SANs: mcp.com.ai, contabo.run.mcp.com.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of contabo.run.mcp.com.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 3799 8 Verified
com.ai. No DS Delegated
mcp.com.ai. 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://contabo.run.mcp.com.ai/mcp Verified 200
http (plaintext) http://contabo.run.mcp.com.ai/mcp HTTPS enforced 301 https://contabo.run.mcp.com.ai/mcp
MCP tools · 124 exposed · ~10,381 tokens

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 →

Tool Tokens
revokeCancelDomain ~51

Revoke cancellation for a specific domain - Revoke cancellation for a specific domain

NameTypeReqDescription
domainstringyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

revokeDomainTransferOut ~52

Revoke transfer out for a domain - Revoke transfer out for a domain

NameTypeReqDescription
domainstringyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

rollbackSnapshot ~96

Revert the instance to a particular snapshot based on its identifier - Rollback the instance to a specific snapshot. In case the snapshot is not the latest one, it will automatically delete all the newer snapshots of the instance

NameTypeReqDescription
instanceIdintegeryes–
rollbackSnapshotBodyobjectyes–
snapshotIdstringyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

setDefaultHandle ~44

Set default handle - Set default handle

NameTypeReqDescription
handleIdstringyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

shutdown ~84

Shutdown compute instance / resource by its id - Shutdown an compute instance / resource. This is similar to pressing the power button on a physical machine. This will send an ACPI event for the guest OS, which should then proceed to a clean shutdown.

NameTypeReqDescription
instanceIdintegeryes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

start ~89

Start a compute instance / resource identified by its id - Starting a compute instance / resource is like powering on a real server. If the compute instance / resource is already started nothing will happen. You may check the current status anytime when getting information about a compute instance / resource.

NameTypeReqDescription
instanceIdintegeryes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

stop ~116

Stop compute instance / resource by its id - Stopping a compute instance / resource is like powering off a real server. So please be aware that data may be lost. Alternatively you may log in and shut your compute instance / resource gracefully via the operating system. If the compute instance / resource is already stopped nothing will happen. You may check the current status anytime when getting information about a compute instance / resource.

NameTypeReqDescription
instanceIdintegeryes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

tool_search ~108

Search the available tool catalog to discover tools by name, description, or arguments. Use a regex pattern or natural language query to find relevant tools. Returns tool references that are automatically expanded into full tool definitions.

NameTypeReqDescription
modestring–Search mode: "regex" for pattern matching, "bm25" for natural language. Defaults to "bm25".
querystringyesA regex pattern or natural-language query to search tool names, descriptions, and argument names. Maximum 200 characters.

No output schema declared.

No examples provided.

unassignInstancePrivateNetwork ~63

Remove instance from a Private Network - Remove a specific instance from a Private Network

NameTypeReqDescription
instanceIdintegeryes–
privateNetworkIdintegeryes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

unassignIp ~81

Unassign a VIP to a VPS/VDS/Bare Metal - Unassign a VIP from an VPS/VDS/Bare Metal using the machine id.

NameTypeReqDescription
ipstringyes–
resourceIdintegeryes–
resourceTypestringyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

updateDnsZoneRecord ~68

Update DNS zone record - Create resource record in a zone

NameTypeReqDescription
recordIdintegeryes–
updateDnsZoneRecordBodyobjectyes–
x-request-idstringyes–
x-trace-idstring––
zoneNamestringyes–

No output schema declared.

No examples provided.

updateDomain ~58

Update a specific domain - Update nameservers and handles for a specific domain

NameTypeReqDescription
domainstringyes–
updateDomainBodyobjectyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

updateHandle ~52

Update specific handle - Update specific handle

NameTypeReqDescription
handleIdstringyes–
updateHandleBodyobjectyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

updateImage ~59

Update custom image name by its id - Update name of the custom image

NameTypeReqDescription
imageIdstringyes–
updateImageBodyobjectyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

updateObjectStorage ~71

Modifies the display name of object storage - Modifies the display name of object storage. Display name must be unique.

NameTypeReqDescription
objectStorageIdstringyes–
updateObjectStorageBodyobjectyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

updatePtrRecord ~62

Edit a PTR Record by ip address - Edit attributes for a specific PTR Record

NameTypeReqDescription
ipAddressstringyes–
updatePtrRecordBodyobjectyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

updateRole ~72

Update specific role by id - Update attributes to your role. Attributes are optional. If not set, the attributes will retain their original values.

NameTypeReqDescription
roleIdintegeryes–
updateRoleBodyobjectyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

updateSecret ~80

Update specific secret by id - Update attributes to your secret. Attributes are optional. If not set, the attributes will retain their original values. Only name and value can be updated.

NameTypeReqDescription
secretIdintegeryes–
updateSecretBodyobjectyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

updateSnapshot ~89

Update specific snapshot by id - Update attributes of a snapshot. You may only specify the attributes you want to change. If an attribute is not set, it will retain its original value.

NameTypeReqDescription
instanceIdintegeryes–
snapshotIdstringyes–
updateSnapshotBodyobjectyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

updateTag ~72

Update specific tag by id - Update attributes to your tag. Attributes are optional. If not set, the attributes will retain their original values.

NameTypeReqDescription
tagIdintegeryes–
updateTagBodyobjectyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

updateUser ~81

Update specific user by id - Update attributes of a user. You may only specify the attributes you want to change. If an attribute is not set, it will retain its original value.

NameTypeReqDescription
updateUserBodyobjectyes–
userIdstringyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

upgradeInstance ~76

Upgrading instance capabilities - In order to enhance your instance with additional features you can purchase add-ons. Currently only firewalling and private network addon is allowed.

NameTypeReqDescription
instanceIdintegeryes–
upgradeInstanceBodyobjectyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

upgradeObjectStorage ~96

Upgrade object storage size resp. update autoscaling settings. - Upgrade object storage size. You can also adjust the autoscaling settings for your object storage. Autoscaling allows you to automatically purchase storage capacity on a monthly basis up to the specified limit.

NameTypeReqDescription
objectStorageIdstringyes–
upgradeObjectStorageBodyobjectyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

validateDomainAvailability ~51

Check domain availablility - Check if a specific domain is available or not

NameTypeReqDescription
domainstringyes–
x-request-idstringyes–
x-trace-idstring––

No output schema declared.

No examples provided.

Install

How do I install the Contabo (VPS) MCP Server server?

Contabo (VPS) MCP Server is a hosted endpoint at https://contabo.run.mcp.com.ai/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 · contabo.run.mcp.com.ai

# add to Claude Code
claude mcp add --transport http ai-com-mcp-contabo 'https://contabo.run.mcp.com.ai/mcp'
Common questions

What is the Contabo (VPS) MCP Server server?

Contabo (VPS) MCP Server is listed in the public MCP registry as ai.com.mcp/contabo. Contabo API (v1.0.0) as MCP tools for cloud provisioning, and management. Powered by HAPI MCP server. This page covers its hosted endpoint (https://contabo.run.mcp.com.ai/mcp).

Is the Contabo (VPS) MCP Server server safe to use?

Contabo (VPS) MCP Server scores 0 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 Contabo (VPS) MCP Server server expose?

Contabo (VPS) MCP Server exposes 124 tools: tool_search, retrieveTagList, createTag, retrieveTag, updateTag, and 119 more. Their descriptions and schemas cost roughly 10,381 tokens of context every time the server is loaded.

Does the Contabo (VPS) MCP Server server require authentication?

No. We connected to Contabo (VPS) MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Contabo (VPS) MCP Server server still maintained?

Contabo (VPS) MCP Server has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 6 August 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 Contabo (VPS) MCP Server server?

VerifyMCP ran 5 checks on Contabo (VPS) MCP Server, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Contabo (VPS) MCP Server: Authorization, Schema quality, Stability, Tool coverage and 2 more. 4 categories score 0 for that reason, because we only credit what we can confirm. 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.