Scalix Cloud
REMOTE · API.SCALIX.WORLD · SCANNED SEP 20
The agent-native cloud: database, functions, AI, storage, computers. 50 tools, one API key.
Available components
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 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 3933 tokens (~74/item across 53 items; 51 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management96
- Stability check failed: schema churn in the 30 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 52 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
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'
{
"mcpServers": {
"world-scalix-cloud": {
"url": "https://api.scalix.world/v1/mcp"
}
}
} {
"servers": {
"world-scalix-cloud": {
"type": "http",
"url": "https://api.scalix.world/v1/mcp"
}
}
} [mcp_servers.world-scalix-cloud] url = "https://api.scalix.world/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"world-scalix-cloud": {
"type": "remote",
"url": "https://api.scalix.world/v1/mcp",
"enabled": true
}
}
} openclaw mcp add world-scalix-cloud --url 'https://api.scalix.world/v1/mcp' --transport streamable-http
mcp_servers:
world-scalix-cloud:
url: "https://api.scalix.world/v1/mcp" {
"McpServers": {
"world-scalix-cloud": {
"Transport": "http",
"Url": "https://api.scalix.world/v1/mcp"
}
}
} assistant mcp add world-scalix-cloud -t streamable-http -u 'https://api.scalix.world/v1/mcp'
{
"mcpServers": {
"world-scalix-cloud": {
"type": "http",
"url": "https://api.scalix.world/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 13 Sept 26 0
- Stability: unverified → fail ▼ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 12 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 85 to 96.
- 4 Sept 26 0
- A breaking change shipped without a version bump: still 1.4.1 ▼ security
- Tool “scalix_search” was removed ▼ security
- Tool “scalix_usage” was removed ▼ security
- “scalix_fn_deploy” reworded the description of “runtime” cosmetic
- 3 Sept 26 0
- Tool “scalix_ai_infer” rewrote its description, which is the text the model reads security
- Tool “scalix_ai_models” rewrote its description, which is the text the model reads security
- “scalix_ai_infer” reworded the description of “model” cosmetic
- 26 Aug 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63.
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 20 Sept 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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| 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 | Yes |
| Resource | https://api.scalix.world/v1/mcp |
| Authorisation server | https://api.scalix.world |
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_upload ~71
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) |
No output schema declared.
No examples provided.
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. 50 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 94 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 51 tools: scalix_db_relationships, scalix_db_search_columns, scalix_db_pii, scalix_db_optimize, scalix_db_text_to_sql, and 46 more. Their descriptions and schemas cost roughly 3,910 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.