Scalix Cloud
REMOTE · API.SCALIX.WORLD
The agent-native cloud: database, functions, AI, storage, computers. 51 tools, one API key.
Available components
Last scanned (12 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
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 Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 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 4405 tokens (~80/item across 55 items; 53 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- All 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 54 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 25 Oct 26 0
- Tool “scalix_project_list” rewrote its description, which is the text the model reads security
- “scalix_project_list” reworded the description of “org_id” cosmetic
- “scalix_project_list” made “org_id” optional cosmetic
- 23 Oct 26 −3
- Authorization: pass → fail ▼ security
- 17 Oct 26 0
- “scalix_db_query” added an optional parameter “timeline_id” cosmetic
- “scalix_computer_exec” reworded the description of “timeout_ms” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 16 Oct 26 0
- New tool “scalix_storage_delete_bucket”, which the server declares destructive security
- New tool “scalix_storage_delete_object”, which the server declares destructive security
- “scalix_storage_create_bucket” added an optional parameter “bucket” cosmetic
- “scalix_storage_download” added an optional parameter “name” cosmetic
- “scalix_storage_list” added an optional parameter “name” cosmetic
- “scalix_storage_upload” added an optional parameter “name” cosmetic
- “scalix_computer_exec” reworded the description of “args” cosmetic
- “scalix_computer_exec” reworded the description of “command” cosmetic
- “scalix_storage_create_bucket” reworded the description of “name” cosmetic
- “scalix_storage_list” reworded the description of “bucket” cosmetic
- 14 Oct 26 0
- Tool “scalix_sandbox_run” rewrote its description, which is the text the model reads security
- 13 Oct 26 +1
- Stability: 0.97 → pass security
- 12 Oct 26 −1
- Stability: pass → 0.97 functional
- 4 Oct 26 +1
- Stability: fail → pass ▲ security
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 · Probed https://api.scalix.world/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=scalix.world | CN=YR1,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | RSA 2048 | SHA256-RSA | 586df21617e318373ebbb2023aaabe6ffae |
| SANs: *.auth.scalix.world, *.db.scalix.world, *.fn.scalix.world, *.run.scalix.world, *.store.scalix.world, api.scalix.world, console.scalix.world, docs.scalix.world, prime.scalix.world, scalix.world, www.scalix.world | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.scalix.world. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| world. | present | 13081 | 8 | Verified |
| scalix.world. | present | 42985 | 13 | Verified |
| api.scalix.world. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="https://docs.scalix.world/mcp", resource_metadata="https://api.scalix.world/.well-known/oauth-protected-resource/v1/mcp", error="invalid_token", error_description="authenticate with an OAuth grant or a Scalix API key"
Bearer realm="https://docs.scalix.world/mcp", resource_metadata="https://api.scalix.world/.well-known/oauth-protected-resource/v1/mcp", error="invalid_token", error_description="authenticate with an OAuth grant or a Scalix API key" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://api.scalix.world/.well-known/oauth-protected-resource/v1/mcp |
|---|---|
| Retrieved | No |
| Problem | metadata_http_error |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.scalix.world/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.scalix.world/v1/mcp | HTTPS enforced | 301 | https://api.scalix.world/v1/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 →
scalix_storage_download ~60
Download an object from storage. Returns the content as base64.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | Bucket name |
| key | string | yes | Object key (path) |
| name | string | – | Alias of bucket — accepted for symmetry with create/delete |
No output schema declared.
No examples provided.
scalix_storage_list ~75
List storage buckets, or list objects in a specific bucket with optional prefix filter.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Bucket name (aliases: name). If omitted, lists all buckets. |
| name | string | – | Alias of bucket — accepted for symmetry with create/delete |
| prefix | string | – | Filter objects by key prefix |
No output schema declared.
No examples provided.
scalix_storage_upload ~88
Upload content to object storage. Provide the content as a base64-encoded string.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | yes | Target bucket name |
| content | string | yes | Base64-encoded file content |
| content_type | string | – | MIME type |
| key | string | yes | Object key (path) |
| name | string | – | Alias of bucket — accepted for symmetry with create/delete |
No output schema declared.
No examples provided.
How do I install the Scalix Cloud MCP server?
Scalix Cloud is a hosted endpoint at https://api.scalix.world/v1/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 · api.scalix.world
claude mcp add --transport http world-scalix-cloud 'https://api.scalix.world/v1/mcp'
What is the Scalix Cloud MCP server?
Scalix Cloud is an MCP server listed in the public MCP registry as world.scalix/cloud. The agent-native cloud: database, functions, AI, storage, computers. 51 tools, one API key. This page covers its hosted endpoint (https://api.scalix.world/v1/mcp).
Is the Scalix Cloud MCP server safe to use?
Scalix Cloud scores 92 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 Scalix Cloud MCP server expose?
Scalix Cloud exposes 53 tools: scalix_db_relationships, scalix_db_search_columns, scalix_db_pii, scalix_db_optimize, scalix_db_text_to_sql, and 48 more. Their descriptions and schemas cost roughly 4,382 tokens of context every time the server is loaded.
Does the Scalix Cloud MCP server require authentication?
Yes. Scalix Cloud asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Scalix Cloud MCP server still maintained?
Scalix Cloud 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.