Servidor MCP de Scalix World

• Nombre en el registroworld.scalix/cloudverificado en el registro MCP

El nombre en el registro está bajo scalix.world. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-19
• Herramientas53
• El servidor se llamascalix-cloud
• Versión del servidor1.5.0
• Versión del protocolo2025-06-18

El 2026-10-19 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 589 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 3 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 3 hasta ahora
• Uso2 estrellas en GitHub
• Respondiómidiendo3 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta753 ms
• Espacio en el contexto del agente≈ 6366 tokenslas definiciones de todas sus herramientas (53), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100
• Resultados tipados0 de 53 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Todas las herramientas pasan las seis comprobaciones.

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• scalix_db_relationships

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

• scalix_db_search_columns

  Search for columns by name or type across all tables.

• scalix_db_pii

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

• scalix_db_optimize

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

• scalix_db_text_to_sql

  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…

• scalix_db_query

  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…

• scalix_db_schema

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

• scalix_db_table

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

• scalix_db_migrate

  Apply a database migration by version number.

• scalix_storage_list

  List storage buckets, or list objects in a specific bucket with optional prefix filter.

• scalix_storage_upload

  Upload content to object storage. Provide the content as a base64-encoded string.

• scalix_storage_download

  Download an object from storage. Returns the content as base64.

• scalix_storage_create_bucket

  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…

• scalix_storage_delete_object

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

• scalix_storage_delete_bucket

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

• scalix_fn_list

  List all deployed serverless functions.

• scalix_fn_deploy

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

• scalix_fn_invoke

  Invoke a deployed function with a JSON payload.

• scalix_kv_get

  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.

• scalix_kv_set

  Set a key-value pair with optional TTL.

• scalix_kv_list

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

• scalix_ai_infer

  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.

• scalix_ai_models

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

• scalix_events_publish

  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.

• scalix_events_topics

  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.

• scalix_cron_create

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

• scalix_sandbox_run

  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).

• scalix_computer_create

  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…

• scalix_computer_set_ssh_keys

  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…

• scalix_computer_list

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

• scalix_computer_exec

  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.

• scalix_computer_write_file

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

• scalix_computer_read_file

  Read a text file out of a persistent Linux machine.

• scalix_computer_stop

  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.

• scalix_computer_start

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

• scalix_computer_delete

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

• scalix_crew_list

  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.

• scalix_crew_board_read

  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…

• scalix_crew_board_post

  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…

• scalix_domain_add

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

• scalix_domain_list

  List all custom domains and their SSL/verification status.

• scalix_domain_verify

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

• scalix_build_create

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

• scalix_build_status

  Get the status and logs of a build.

• scalix_project_create

  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…

• scalix_project_list

  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. Needs an admin API key: organization admin scope is never delegated to a connected app…

• scalix_auth_configure

  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…

• scalix_status

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

• scalix_run_deploy

  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…

• scalix_run_list

  List all deployed container services in the project.

• scalix_run_scale

  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…

• scalix_run_rollback

  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…

• scalix_run_delete

  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…