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.

Scalix Cloud

REMOTE · API.SCALIX.WORLD

The agent-native cloud: database, functions, AI, storage, computers. 51 tools, one API key.

Available components

0 this week 92 Trust /100

Last scanned (2 hours ago)

Scores higher than 99% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Cloud Infrastructure

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 Security91
Transport & Reachability100
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
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.

  • 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
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 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
MCP tools · 53 exposed · ~4,382 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
scalix_ai_infer ~138

Run AI inference on Scalix AI. Sends a prompt and returns the model's response in the OpenAI-compatible chat-completions format; tokens are billed to the project's credit pool. Discover available model IDs with scalix_ai_models.

NameTypeReqDescription
max_tokensinteger–Maximum tokens to generate
modelstring–Model ID (from scalix_ai_models — a scalix-auto/* tier or a scalix-gw/<vendor>/<model> catalog id)
promptstringyesUser prompt / message
systemstring–System message
temperaturenumber–Sampling temperature (0-2)

No output schema declared.

No examples provided.

scalix_ai_models ~38

List the AI models available to the project — virtual tiers and the pass-through catalog model IDs — for use in scalix_ai_infer.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scalix_auth_configure ~116

Configure end-user authentication for the project — require MFA, require email confirmation, and set the allowed auth providers. Needs an admin API key: organization admin scope is never delegated to a connected app, so this tool fails on an OAuth connection.

NameTypeReqDescription
allowed_providersarray–Allowed auth providers (e.g., ["email", "google", "github"])
mfa_enabledboolean–Require multi-factor authentication
require_email_confirmationboolean–Require users to confirm their email before a session is issued

No output schema declared.

No examples provided.

scalix_build_create ~67

Create a new container image build from a Git repository or Dockerfile.

NameTypeReqDescription
branchstring–Git branch
dockerfilestring–Path to Dockerfile in repo
git_urlstringyesGit repository URL
namestringyesBuild name

No output schema declared.

No examples provided.

scalix_build_status ~31

Get the status and logs of a build.

NameTypeReqDescription
build_idstringyesBuild ID to check

No output schema declared.

No examples provided.

scalix_computer_create ~318

Get or create a persistent Linux machine by name. Idempotent — calling it again with the same name returns the existing machine rather than creating another, so it is safe to retry. Unlike a sandbox, the disk survives stop/start and is only erased by scalix_computer_delete.

NameTypeReqDescription
disk_gbinteger–Root disk in GB, 5-200 (default 10). Fixed at create — disks do not grow. Ignored if the machine already exists.
memory_mbinteger–Memory in MB, 512-32768 (default 1024). Ignored if the machine already exists.
namestringyesMachine name: lowercase letters, digits and hyphens, max 63 characters. Unique to you.
ssh_keysarray–OpenSSH public keys to authorise for root, max 32, e.g. ["ssh-ed25519 AAAAC3Nz… you@laptop"]. Only needed if a human will ssh in — exec, write_file and read_file all work without one. Send the public…
vcpusinteger–vCPUs, 1-16 (default 1). Ignored if the machine already exists.

No output schema declared.

No examples provided.

scalix_computer_delete ~50

Permanently delete a persistent Linux machine AND its disk. This cannot be undone — use scalix_computer_stop if you may want the files back.

NameTypeReqDescription
idstringyesMachine id

No output schema declared.

No examples provided.

scalix_computer_exec ~219

Run a command inside a persistent Linux machine and wait for it to finish. Returns exit code, stdout and stderr. The machine must be running.

NameTypeReqDescription
argsarray–Arguments passed to the program; omit when command is a shell string
commandstringyesEither a bare program (e.g. bash, with args passed separately) OR a full shell string (e.g. "apt-get install -y jq") — a command containing whitespace is run via sh -lc automatically, so no manual ["…
cwdstring–Working directory inside the machine
envobject–Environment variables for this command only
idstringyesMachine id from scalix_computer_create or scalix_computer_list
timeout_msinteger–Give up after this many milliseconds, 1000-300000 (default 120000). 300s is the platform-wide hop ceiling — a larger request is served at 300s, not rejected.

No output schema declared.

No examples provided.

scalix_computer_list ~25

List your persistent Linux machines with their status, address and resource shape.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scalix_computer_read_file ~44

Read a text file out of a persistent Linux machine.

NameTypeReqDescription
idstringyesMachine id
pathstringyesAbsolute path inside the machine

No output schema declared.

No examples provided.

scalix_computer_set_ssh_keys ~128

Replace the ssh keys authorised for root on a persistent Linux machine. This is how you revoke: send the list without the key you want gone, and on a running machine it stops working immediately. Sending an empty list removes every key. Not a patch — whatever you send becomes the whole list, so read the current keys from scalix_computer_list first if you mean to add one.

NameTypeReqDescription
idstringyesMachine id
ssh_keysarrayyesThe complete list of OpenSSH public keys, max 32. Empty array removes all of them.

No output schema declared.

No examples provided.

scalix_computer_start ~33

Start a stopped persistent Linux machine. Same disk, same address.

NameTypeReqDescription
idstringyesMachine id

No output schema declared.

No examples provided.

scalix_computer_stop ~63

Stop a persistent Linux machine. The disk and the network address are kept, so starting it again returns the same files at the same address. Stop machines you are done with — a stopped machine costs only its disk.

NameTypeReqDescription
idstringyesMachine id

No output schema declared.

No examples provided.

scalix_computer_write_file ~111

Write a text file into a persistent Linux machine. Use this instead of shelling out with cat/echo — no quoting to get wrong.

NameTypeReqDescription
contentstringyesFile contents as text
idstringyesMachine id
modeinteger–Unix mode in decimal, e.g. 493 for 0755. Omit unless the file must be executable.
pathstringyesAbsolute path inside the machine, e.g. /root/app/main.py

No output schema declared.

No examples provided.

scalix_crew_board_post ~231

Post a note to the crew's notice board for other members and the human to see. The board is news, not knowledge: set ttl_seconds so routine updates expire on their own, pin only what every future task must see, and set owner_member_id to hand work off to a specific member. Notes cannot be edited from here — post a correction instead.

NameTypeReqDescription
author_member_idstring–Your member id, so the note is attributed. Omit when posting as the human.
bodystringyesThe note, max 8000 chars. Write for a teammate who was not watching your work.
crew_idstringyesCrew id from scalix_crew_list
owner_member_idstring–Hand off: the member id now responsible for this item.
pinnedboolean–Keep this in front of everyone indefinitely. Default false; most notes should expire instead.
ttl_secondsinteger–Seconds until the note expires, 60 to 7776000 (90 days). Omit for no expiry — usually only right for pins.

No output schema declared.

No examples provided.

scalix_crew_board_read ~90

Read a crew's notice board: every pinned note plus the newest unpinned ones, current as of this call. The board is the crew's shared coordination state — read it before starting work so you act on the latest news, and post what teammates need to know with scalix_crew_board_post.

NameTypeReqDescription
crew_idstringyesCrew id from scalix_crew_list

No output schema declared.

No examples provided.

scalix_crew_list ~43

List your crews with their ids and names. A crew is a team of AI members that share a notice board; use the crew id with the board tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scalix_cron_create ~82

Create a cron schedule to run a function or webhook on a timer.

NameTypeReqDescription
action_typestringyesType of action to trigger
configobject–Action configuration (function_id or webhook URL)
expressionstringyesCron expression (e.g., '*/5 * * * *')
namestringyesSchedule name

No output schema declared.

No examples provided.

scalix_db_migrate ~40

Apply a database migration by version number.

NameTypeReqDescription
tenant_idstringyesTenant ID
versionstringyesMigration version to apply

No output schema declared.

No examples provided.

scalix_db_optimize ~40

Analyze a SQL query and return optimization suggestions including index recommendations and query rewrites.

NameTypeReqDescription
sqlstringyesSQL query to analyze and optimize

No output schema declared.

No examples provided.

scalix_db_pii ~24

List all columns classified as containing personally identifiable information (PII).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scalix_db_query ~202

Execute a SQL query against the project database. Returns columns, rows, row count, and cost breakdown. Destructive statements (DROP/TRUNCATE/bulk DELETE) require a two-step confirmation: the first call returns code CONFIRMATION_REQUIRED with a confirmation_token — re-call with that value in confirm_token to execute.

NameTypeReqDescription
confirm_tokenstring–Confirmation token from a prior CONFIRMATION_REQUIRED response; required to execute destructive SQL (single-use, short TTL)
paramsarray–Bind parameters for the query
sqlstringyesSQL query to execute
timeline_idstring–F17: run the query against a BRANCH timeline of this project instead of the primary. Takes the timeline_id returned by scalix_db_branch_create (or its db_<timeline_id> form). A timeline that is not a…

No output schema declared.

No examples provided.

scalix_db_relationships ~24

Get the relationship map showing how tables are connected via foreign keys.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scalix_db_schema ~26

Get the full database schema including all tables, columns, types, and relationships.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scalix_db_search_columns ~37

Search for columns by name or type across all tables.

NameTypeReqDescription
querystringyesSearch term to match column names or types

No output schema declared.

No examples provided.

scalix_db_table ~38

Get detailed information about a specific database table including columns, indexes, and foreign keys.

NameTypeReqDescription
tablestringyesTable name to inspect

No output schema declared.

No examples provided.

scalix_db_text_to_sql ~131

Translate a plain-language question into a candidate SQL query using pattern-matching against the live schema (no AI model — simple questions only: counts, averages, filtered selects on a named table). Returns the SQL without executing it, with a confidence score; low confidence means the table was guessed. Review the statement and tables_used, then run it with scalix_db_query. For complex questions, read scalix_db_schema and write the SQL directly.

NameTypeReqDescription
questionstringyesThe question to answer from the database, in plain language (e.g. 'how many orders shipped last week?')

No output schema declared.

No examples provided.

scalix_domain_add ~42

Add a custom domain to the project. Returns DNS records to configure.

NameTypeReqDescription
domainstringyesDomain name to add (e.g., api.example.com)

No output schema declared.

No examples provided.

scalix_domain_list ~21

List all custom domains and their SSL/verification status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scalix_domain_verify ~32

Verify DNS configuration for a custom domain and provision SSL certificate.

NameTypeReqDescription
domainstringyesDomain to verify

No output schema declared.

No examples provided.

scalix_events_publish ~85

Publish an event to a topic. Provide an event_type (a short name for the kind of event, e.g. 'user.created') and the data payload.

NameTypeReqDescription
dataobjectyesEvent payload (JSON)
event_typestringyesEvent type/name, e.g. 'user.created'
topic_idstringyesTopic ID to publish to

No output schema declared.

No examples provided.

scalix_events_topics ~53

List the event-bus topics in the project, with each topic's ID and name. Use this to find or verify a topic_id before publishing with scalix_events_publish; publishing to a non-existent topic fails.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scalix_fn_deploy ~91

Deploy a Scalix Function — serverless, per-request billed, running in isolated microVMs — from a container image. Invoke it with scalix_fn_invoke once deployed.

NameTypeReqDescription
imagestringyesContainer image reference
namestringyesFunction name
runtimestring–Runtime — `node` or `python` (exactly what the functions orchestrator accepts)

No output schema declared.

No examples provided.

scalix_fn_invoke ~46

Invoke a deployed function with a JSON payload.

NameTypeReqDescription
dataobject–JSON payload to pass to the function
function_idstringyesFunction ID to invoke

No output schema declared.

No examples provided.

scalix_fn_list ~17

List all deployed serverless functions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scalix_kv_get ~75

Read a single value from the project's key-value store by exact key. Returns the stored value, or a not-found error if the key does not exist or its TTL has expired. Use scalix_kv_list to discover keys by prefix first.

NameTypeReqDescription
keystringyesExact key to look up (case-sensitive)

No output schema declared.

No examples provided.

scalix_kv_list ~35

List keys in the key-value store, optionally filtered by prefix.

NameTypeReqDescription
prefixstring–Filter keys by prefix

No output schema declared.

No examples provided.

scalix_kv_set ~57

Set a key-value pair with optional TTL.

NameTypeReqDescription
keystringyesKey to set
ttlinteger–Time-to-live in seconds (0 = no expiry)
valuestringyesValue to store

No output schema declared.

No examples provided.

scalix_project_create ~95

Create a new project within an organization. Returns the project ID, name, and slug. Issue an API key for the new project separately. Needs an admin API key: organization admin scope is never delegated to a connected app, so this tool fails on an OAuth connection.

NameTypeReqDescription
namestringyesProject display name
org_idstringyesOrganization ID
slugstringyesURL-safe project slug

No output schema declared.

No examples provided.

scalix_project_list ~122

List every project in an organization, with each project's ID, name, and slug. Use this to resolve a project ID before calling project-scoped tools. `org_id` is optional: omit it to list the projects of the organization the API key belongs to (resolved via GET /v1/me). Needs an admin API key: organization admin scope is never delegated to a connected app, so this tool fails on an OAuth connection.

NameTypeReqDescription
org_idstring–Organization ID whose projects to list. Optional — defaults to the API key's own organization.

No output schema declared.

No examples provided.

scalix_run_delete ~98

Permanently delete a Scalix Run service. This cannot be undone: it stops the running instances, releases the public HTTPS URL, erases any attached volumes and discards every revision, so scalix_run_rollback cannot bring it back afterwards. To stop paying for an idle service without losing it, set min_instances to 0 with scalix_run_scale instead.

NameTypeReqDescription
idstringyesService ID (from scalix_run_list)

No output schema declared.

No examples provided.

scalix_run_deploy ~201

Deploy a long-running container service on Scalix Run from a container image. Creates a new service, or a new revision of an existing service with the same name, with health checks, a public HTTPS URL, and autoscaling between min_instances and max_instances (min 0 = scale-to-zero when idle). Billed per vCPU-hour while instances run. Roll back a bad revision with scalix_run_rollback.

NameTypeReqDescription
envobject–Environment variables as key-value pairs
imagestringyesContainer image from the Scalix registry ({registry}/{project_id}/{repo}:{tag}). External registries (Docker Hub, etc.) are NOT supported — build & push first with scalix_build_create.
max_instancesinteger–Maximum instances
min_instancesinteger–Minimum instances (0 = scale to zero)
namestringyesService name
portinteger–Port the container listens on

No output schema declared.

No examples provided.

scalix_run_list ~19

List all deployed container services in the project.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scalix_run_rollback ~102

Roll a Scalix Run service back to an earlier revision — omit 'revision' to return to the immediately previous one. Traffic switches to the target revision; the replaced revision is kept and can be redeployed later. Use scalix_run_list to see services and their current revisions.

NameTypeReqDescription
idstringyesService ID (from scalix_run_list)
revisioninteger–Revision number to roll back to; omit for the immediately previous revision

No output schema declared.

No examples provided.

scalix_run_scale ~119

Change the autoscaling bounds of an existing Scalix Run service without redeploying it. Raising min_instances keeps instances warm (no cold starts, higher cost); min_instances 0 enables scale-to-zero when idle. Takes effect immediately. Find service IDs with scalix_run_list.

NameTypeReqDescription
idstringyesService ID (from scalix_run_list)
max_instancesinteger–New maximum instance count the service may scale up to
min_instancesinteger–New minimum instance count (0 = scale-to-zero when idle)

No output schema declared.

No examples provided.

scalix_sandbox_run ~120

Execute code in an isolated sandbox. Supports Python, JavaScript, TypeScript, and Bash. Returns stdout/stderr, the probed interpreter version, and any files the code wrote (base64, under size/count caps).

NameTypeReqDescription
codestringyesSource code to execute
filesobject–Additional files (filename -> content)
languagestringyesProgramming language
packagesarray–Packages to install (pip/npm)
timeout_secondsinteger–Max execution time in seconds (default: 30)

No output schema declared.

No examples provided.

scalix_status ~25

Get the current health status of the Scalix Cloud platform including all service components.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scalix_storage_create_bucket ~200

Create a new Scalix Storage bucket in the project (S3-compatible object storage). Bucket names must be unique within the project. Setting public=true makes every object in the bucket readable without authentication — leave it false (the default) and use presigned URLs for private sharing. Public buckets double as static websites: upload index.html and serve it from the project's store subdomain at https://{slug}.store.scalix.world/buckets/{bucket}/objects/ (directory requests serve index.html; a 404.html object is served as the error page).

NameTypeReqDescription
bucketstring–Alias of name — accepted for symmetry with the object tools
namestringyesBucket name, unique within the project (aliases: bucket)
publicboolean–true = all objects publicly readable without auth (also serves as a static website on {slug}.store.scalix.world); false (default) = private, share via presigned URLs

No output schema declared.

No examples provided.

scalix_storage_delete_bucket ~50

Permanently delete a storage bucket and every object in it. Irreversible.

NameTypeReqDescription
bucketstringyesBucket name (aliases: name)
namestring–Alias of bucket

No output schema declared.

No examples provided.

scalix_storage_delete_object ~65

Permanently delete an object (key) from a storage bucket. Irreversible.

NameTypeReqDescription
bucketstringyesBucket name (aliases: name)
keystringyesObject key (path) to delete
namestring–Alias of bucket

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http world-scalix-cloud 'https://api.scalix.world/v1/mcp'
Common questions

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.