IONOS CLOUD MCP Server
OCI · GHCR.IO/IONOS-CLOUD/IONOSCLOUD-MCP
Inspect and manage IONOS CLOUD infrastructure via MCP. Writes are opt-in and off by default.
Available components
Last scanned (9 hours ago)
Scores higher than 77% of OCI servers
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 14 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability89
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 9893 tokens (~83/item across 119 items; 118 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 118 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 119 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 44
First indexed and scored.
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 5 Nov 2026 · Analysed oci/ghcr.io/ionos-cloud/ionoscloud-mcp@1.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
get_server ~68
Get details of a specific server
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1 for list operations) |
| server_id | string | yes | the ID of the server |
No output schema declared.
No examples provided.
get_server_gpu ~79
Get details of a specific GPU attached to a server
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5) |
| gpu_id | string | yes | the ID of the GPU |
| server_id | string | yes | the ID of the server |
No output schema declared.
No examples provided.
get_server_remote_console ~73
Get the remote console URL for a specific server
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1 for list operations) |
| server_id | string | yes | the ID of the server |
No output schema declared.
No examples provided.
get_snapshot ~46
Get details of a specific snapshot
| Name | Type | Req | Description |
|---|---|---|---|
| depth | null|integer | – | nesting depth of returned objects (0-5) |
| snapshot_id | string | yes | the ID of the snapshot |
No output schema declared.
No examples provided.
get_target_group ~50
Get details of a specific target group
| Name | Type | Req | Description |
|---|---|---|---|
| depth | null|integer | – | nesting depth of returned objects (0-5) |
| target_group_id | string | yes | the ID of the target group |
No output schema declared.
No examples provided.
get_template ~47
Get details of a specific server template
| Name | Type | Req | Description |
|---|---|---|---|
| depth | null|integer | – | nesting depth of returned objects (0-5) |
| template_id | string | yes | the ID of the template |
No output schema declared.
No examples provided.
get_volume ~61
Get details of a specific volume
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5) |
| volume_id | string | yes | the ID of the volume |
No output schema declared.
No examples provided.
head_object_storage_bucket ~39
Check whether an Object Storage bucket exists and is accessible with the current credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | the name of the object storage bucket |
No output schema declared.
No examples provided.
head_object_storage_object ~77
Check whether an object exists in an Object Storage bucket and retrieve its user-defined metadata (x-amz-meta-* headers). Returns an error if the object does not exist or is not accessible.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | the name of the object storage bucket |
| key | string | yes | the object key (path within the bucket) |
No output schema declared.
No examples provided.
list_activitylog_contracts ~68
List contracts accessible for IONOS CLOUD activity log queries. Primarily useful for reseller and partner users with multiple contracts. Single-contract users can skip this — their contract number is embedded in the JWT token returned by get_billing_profile or visible in the IONOS DCD console.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_activitylog_events ~379
Query the IONOS CLOUD activity log: full audit trail of API requests made against a contract (who did what, when, on which resource). Requires ACCESS_ACTIVITY_LOG privilege on the token. Defaults: last 7 days, limit 25, RequestStatusUpdate events excluded. Use user filter to narrow to a specific account. Use event_types to restrict to e.g. ['Error','RequestAccepted']. Maximum date range is 90 days — paginate or narrow the window for longer spans. Use list_activitylog_contracts first to look up the contract number if needed.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | integer | yes | the contract number whose activity log to query; reseller/partner users get IDs from list_activitylog_contracts, single-contract users read it from their JWT |
| date_end | null|string | – | inclusive end date YYYY-MM-DD; defaults to today when omitted; maximum range is 90 days |
| date_start | null|string | – | inclusive start date YYYY-MM-DD; defaults to 7 days ago when omitted |
| event_types | null|array | – | filter to these event types only (client-side); e.g. ['Error','RequestAccepted'] — omit Provision and RequestStatusUpdate to cut ~65% of typical log volume |
| include_status_updates | null|boolean | – | include RequestStatusUpdate events (default false); these are async provisioning echoes that account for ~55% of log volume and are rarely useful |
| limit | null|integer | – | max events to return; defaults to 25; increase only when the user explicitly asks for bulk data |
| offset | null|integer | – | 0-based pagination offset |
| user | null|string | – | filter by username (client-side); e.g. 'ionosctl-v6@cloud.ionos.com' — drastically reduces output when investigating a specific user |
No output schema declared.
No examples provided.
list_alb_forwarding_rules ~124
List all forwarding rules of an application load balancer
| Name | Type | Req | Description |
|---|---|---|---|
| application_loadbalancer_id | string | yes | the ID of the application load balancer |
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"prod"} If the result is empty, retry without filters — a filter typo or mismatch silently returns nothing. |
No output schema declared.
No examples provided.
list_application_loadbalancers ~108
List all application load balancers (ALB) in a data center
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"prod"} If the result is empty, retry without filters — a filter typo or mismatch silently returns nothing. |
No output schema declared.
No examples provided.
list_billing_evn ~76
Get provisioning itemized data (EVN) for your contract for the current billing month. Shows per-resource usage intervals grouped by datacenter. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | integer | yes | contract number from get_billing_profile |
No output schema declared.
No examples provided.
list_billing_evn_by_period ~139
Get provisioning itemized data (EVN) for a specific billing period (YYYY-MM). One month per call. If the user requests a range longer than one month, calculate the number of monthly calls required, inform the user, and ask for permission before proceeding. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | integer | yes | contract number from get_billing_profile |
| period | string | yes | billing period in YYYY-MM format (e.g. 2026-04). Maximum one month per request — for wider ranges call once per month |
No output schema declared.
No examples provided.
list_billing_invoices ~68
List all invoices for your IONOS CLOUD contract. Returns invoice IDs, dates, and amounts. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | integer | yes | contract number from get_billing_profile |
No output schema declared.
No examples provided.
list_billing_invoices_by_period ~104
List invoices for a specific billing period (YYYY-MM). One month per call. If the user requests a range longer than one month, calculate the number of monthly calls required, inform the user, and ask for permission before proceeding. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | yes | billing period in YYYY-MM format (e.g. 2026-04) |
No output schema declared.
No examples provided.
list_billing_products ~211
Search the IONOS CLOUD product/pricing catalog by keyword. The filter is applied client-side as a case-insensitive partial match on each product's description — it is not an API-level parameter. Returns non-deprecated products whose description contains the filter string. IMPORTANT: Only call this tool when the user has explicitly specified a product or category they want to see pricing for. If the user asks a broad question like 'what are the prices' or 'show me all products', do NOT guess keywords or call this tool multiple times — instead ask the user which specific product or category they are interested in. Examples of valid filters: 'RAM', 'core', 'storage', 'Kubernetes', 'Postgres', 'network', 'Windows'.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | integer | yes | contract number from get_billing_profile |
| filter | string | yes | keyword to filter products by description (e.g. 'RAM', 'Kubernetes', 'Postgres', 'storage'). Use broad terms to find relevant pricing |
No output schema declared.
No examples provided.
list_billing_traffic ~77
Get network traffic data for your contract for the current billing month. Returns per-datacenter and per-NIC inbound/outbound traffic in bytes. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | integer | yes | contract number from get_billing_profile |
No output schema declared.
No examples provided.
list_billing_traffic_by_period ~134
Get network traffic data for a specific billing period (YYYY-MM). One month per call. If the user requests a range longer than one month, calculate the number of monthly calls required, inform the user, and ask for permission before proceeding. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | integer | yes | contract number from get_billing_profile |
| period | string | yes | billing period in YYYY-MM format (e.g. 2026-04). Maximum one month per request — for wider ranges call once per month |
No output schema declared.
No examples provided.
list_billing_usage ~157
Get aggregated resource usage for your contract for the current billing period. Shows metered quantities (CPU hours, GB-hours, etc.) grouped by datacenter. Defaults exclude zero-quantity meters (set include_zero=true to keep them). Filter by datacenter_id to narrow scope. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | integer | yes | contract number from get_billing_profile |
| datacenter_id | null|string | – | scope to a single datacenter (VDC UUID) |
| include_zero | null|boolean | – | include meters with quantity 0 (default false); set true to find datacenters with metered SKUs that didn't consume |
No output schema declared.
No examples provided.
list_billing_utilization ~427
Get per-resource utilization for the current billing period, grouped by datacenter. Defaults exclude zero-quantity meters (set include_zero=true to find idle resources). Use group_by='meter' or 'datacenter' to aggregate further, or top_n=N for a flat global ranking of the largest meters. Filter by datacenter_id, meter_types, or regions to narrow scope. For contracts with many datacenters, scope with regions, datacenter_id, or meter_types — or set top_n=10 for a flat global top-N list — before group_by=datacenter to keep the response under 25 KB. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | integer | yes | contract number from get_billing_profile |
| datacenter_id | null|string | – | scope to a single datacenter (VDC UUID) |
| group_by | null|string | – | aggregation level: omitted or '' = per-resource (default), 'meter' = sum per SKU per datacenter, 'datacenter' = sum per type per datacenter — coarser groupings shrink output but lose detail |
| include_zero | null|boolean | – | include meters with quantity 0 (default false); set true to find existing resources that didn't consume in the window |
| meter_types | null|array | – | filter to these meter type categories only (client-side); e.g. ['DBAAS','DNS','SERVER'] |
| regions | null|array | – | filter to these regions only (client-side); e.g. ['de/fra','es/vit'] |
| top_n | null|integer | – | return only the N largest meters globally, sorted by quantity desc — flat list with dc_id/dc_name on each row, datacenters[] omitted; ideal for cost audits on contracts with many datacenters. When co… |
No output schema declared.
No examples provided.
list_billing_utilization_by_period ~401
Get per-resource utilization for a specific billing period (YYYY-MM). One month per call. If the user requests a range longer than one month, calculate the number of monthly calls required, inform the user, and ask for permission before proceeding. Same compaction flags as list_billing_utilization (include_zero, group_by, datacenter_id, meter_types, regions, top_n). For contracts with many datacenters, scope with regions, datacenter_id, or meter_types — or set top_n=10 for a flat global top-N list — before group_by=datacenter to keep the response under 25 KB. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | integer | yes | contract number from get_billing_profile |
| datacenter_id | null|string | – | scope to a single datacenter (VDC UUID) |
| group_by | null|string | – | aggregation level: omitted or '' = per-resource (default), 'meter' = sum per SKU per datacenter, 'datacenter' = sum per type per datacenter |
| include_zero | null|boolean | – | include meters with quantity 0 (default false) |
| meter_types | null|array | – | filter to these meter type categories only (client-side); e.g. ['DBAAS','DNS','SERVER'] |
| period | string | yes | billing period in YYYY-MM format (e.g. 2026-04). Maximum one month per request — for wider ranges call once per month |
| regions | null|array | – | filter to these regions only (client-side); e.g. ['de/fra'] |
| top_n | null|integer | – | return only the N largest meters globally, sorted by quantity desc (flat list, datacenters[] omitted). When combined with group_by='datacenter', top_meters[] rows have no meter_id |
No output schema declared.
No examples provided.
list_cert_auto_certificates ~26
List all auto-certificates in your IONOS Cloud Certificate Manager account
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_cert_certificates ~39
List all SSL/TLS certificates in your IONOS Cloud Certificate Manager account. Returns certificate metadata and public key material but not the private key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_cert_providers ~35
List all certificate providers in your IONOS Cloud Certificate Manager account. Returns provider configuration but not the external account binding secret.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_datacenters ~125
List all virtual data centers. Returns names and basic properties by default (depth=1).
| Name | Type | Req | Description |
|---|---|---|---|
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1); depth 1 includes names and basic properties |
| filters | object | – | server-side filters as property name to value pairs (contains match); e.g. {"name":"prod","location":"de/fra"}. Filterable properties include: name, description, location, version. If the result is e… |
No output schema declared.
No examples provided.
list_dns_records ~17
List all DNS records across all zones
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_dns_reverse_records ~23
List all reverse DNS records in your IONOS CLOUD account
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_dns_secondary_zone_records ~37
List all DNS records in a specific secondary zone
| Name | Type | Req | Description |
|---|---|---|---|
| secondary_zone_id | string | yes | the ID of the secondary DNS zone |
No output schema declared.
No examples provided.
list_dns_secondary_zones ~24
List all secondary DNS zones in your IONOS CLOUD account
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_dns_zone_dnssec_keys ~36
List DNSSEC keys for a specific DNS zone
| Name | Type | Req | Description |
|---|---|---|---|
| zone_id | string | yes | the ID of the DNS zone |
No output schema declared.
No examples provided.
list_dns_zone_records ~33
List all DNS records in a specific zone
| Name | Type | Req | Description |
|---|---|---|---|
| zone_id | string | yes | the ID of the DNS zone |
No output schema declared.
No examples provided.
list_dns_zones ~22
List all DNS zones in your IONOS CLOUD account
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_firewall_rules ~138
List all firewall rules on a network interface
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"prod","type":"INGRESS","direction":"INBOUND"} If the result is empty, retry without filters — a filter typo or mismatch sil… |
| nic_id | string | yes | the ID of the network interface |
| server_id | string | yes | the ID of the server |
No output schema declared.
No examples provided.
list_images ~108
List all available images (OS templates) in IONOS CLOUD
| Name | Type | Req | Description |
|---|---|---|---|
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"ubuntu","imageType":"HDD","licenceType":"LINUX","location":"de/fra"} If the result is empty, retry without filters — a filt… |
No output schema declared.
No examples provided.
list_ip_blocks ~95
List all reserved IP blocks in your IONOS CLOUD account
| Name | Type | Req | Description |
|---|---|---|---|
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"prod","location":"de/fra"} If the result is empty, retry without filters — a filter typo or mismatch silently returns nothi… |
No output schema declared.
No examples provided.
list_k8s_clusters ~57
List all Kubernetes clusters in your IONOS CLOUD account. Returns names and basic properties by default (depth=1).
| Name | Type | Req | Description |
|---|---|---|---|
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
No output schema declared.
No examples provided.
list_k8s_nodepool_nodes ~92
List all worker nodes in a Kubernetes node pool, including each node's state and public/private IP addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1 for list operations) |
| k8s_cluster_id | string | yes | the ID of the Kubernetes cluster |
| nodepool_id | string | yes | the ID of the Kubernetes node pool |
No output schema declared.
No examples provided.
list_k8s_nodepools ~74
List all node pools in a Kubernetes cluster. A cluster with no node pools runs no workloads.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1 for list operations) |
| k8s_cluster_id | string | yes | the ID of the Kubernetes cluster |
No output schema declared.
No examples provided.
list_k8s_versions ~63
List all available Kubernetes versions in IONOS CLOUD. These are the versions a new cluster or node pool may be created with; to upgrade an existing one, use its availableUpgradeVersions instead (get_k8s_cluster / get_k8s_nodepool).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_lan_nics ~116
List all NICs attached to a specific LAN
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"prod"} If the result is empty, retry without filters — a filter typo or mismatch silently returns nothing. |
| lan_id | string | yes | the ID of the LAN |
No output schema declared.
No examples provided.
list_lans ~100
List all LANs in a data center
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"prod"} If the result is empty, retry without filters — a filter typo or mismatch silently returns nothing. |
No output schema declared.
No examples provided.
list_loadbalancer_nics ~123
List all NICs balanced by a specific load balancer
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"prod"} If the result is empty, retry without filters — a filter typo or mismatch silently returns nothing. |
| loadbalancer_id | string | yes | the ID of the load balancer |
No output schema declared.
No examples provided.
list_loadbalancers ~102
List all load balancers in a data center
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"prod"} If the result is empty, retry without filters — a filter typo or mismatch silently returns nothing. |
No output schema declared.
No examples provided.
list_locations ~89
List all available locations (regions) in IONOS CLOUD
| Name | Type | Req | Description |
|---|---|---|---|
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"Frankfurt"} If the result is empty, retry without filters — a filter typo or mismatch silently returns nothing. |
No output schema declared.
No examples provided.
list_nat_gateway_rules ~121
List all rules of a specific NAT gateway
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"prod","type":"SNAT"} If the result is empty, retry without filters — a filter typo or mismatch silently returns nothing. |
| nat_gateway_id | string | yes | the ID of the NAT gateway |
No output schema declared.
No examples provided.
list_nat_gateways ~101
List all NAT gateways in a data center
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"prod"} If the result is empty, retry without filters — a filter typo or mismatch silently returns nothing. |
No output schema declared.
No examples provided.
list_network_loadbalancers ~108
List all network load balancers (NLB) in a data center
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"prod"} If the result is empty, retry without filters — a filter typo or mismatch silently returns nothing. |
No output schema declared.
No examples provided.
list_nics ~117
List all network interfaces (NICs) attached to a server
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter_id | string | yes | the ID of the data center |
| depth | null|integer | – | nesting depth of returned objects (0-5, default 1) |
| filters | object | – | server-side filters as property→value pairs (contains match); e.g. {"name":"prod"} If the result is empty, retry without filters — a filter typo or mismatch silently returns nothing. |
| server_id | string | yes | the ID of the server |
No output schema declared.
No examples provided.
How do I install the IONOS CLOUD MCP Server server?
IONOS CLOUD MCP Server runs locally as a container image, launched with docker run --rm -i -e IONOS_TOKEN -e IONOS_S3_ACCESS_KEY -e IONOS_S3_SECRET_KEY -e IONOS_MCP_LOAD_MODE -e IONOS_MCP_TOOL_SCOPE ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/ionos-cloud/ionoscloud-mcp
claude mcp add ionos-cloud-ionoscloud-mcp -- docker run --rm -i -e IONOS_TOKEN -e IONOS_S3_ACCESS_KEY -e IONOS_S3_SECRET_KEY -e IONOS_MCP_LOAD_MODE -e IONOS_MCP_TOOL_SCOPE ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.2
This image reads IONOS_TOKEN, IONOS_S3_ACCESS_KEY, IONOS_S3_SECRET_KEY, IONOS_MCP_LOAD_MODE and IONOS_MCP_TOOL_SCOPE. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the IONOS CLOUD MCP Server server?
IONOS CLOUD MCP Server is listed in the public MCP registry as io.github.ionos-cloud/ionoscloud-mcp. Inspect and manage IONOS CLOUD infrastructure via MCP. Writes are opt-in and off by default. This page covers its container image (ghcr.io/ionos-cloud/ionoscloud-mcp).
Is the IONOS CLOUD MCP Server server safe to use?
IONOS CLOUD MCP Server scores 50 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 IONOS CLOUD MCP Server server expose?
IONOS CLOUD MCP Server exposes 118 tools: get_application_loadbalancer, get_billing_focus_spec, get_billing_invoice, get_billing_profile, get_billing_usage_by_datacenter, and 113 more. Their descriptions and schemas cost roughly 9,852 tokens of context every time the server is loaded.
Is the IONOS CLOUD MCP Server server still maintained?
IONOS CLOUD MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the IONOS CLOUD MCP Server server under?
IONOS CLOUD MCP Server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the IONOS CLOUD MCP Server server?
VerifyMCP ran 12 checks on IONOS CLOUD MCP Server, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about IONOS CLOUD MCP Server: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.