Servidor MCP de TrustyCap

• Nombre en el registrocom.trustycap/trustycapverificado en el registro MCP

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

• Estadorespondecomprobado el 2026-10-25
• Herramientas13
• El servidor se llamatrustycap
• Versión del servidor2.0.4
• Versión del protocolo2025-06-18

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

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 2 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: 2 hasta ahora
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta1217 ms
• Espacio en el contexto del agente≈ 3536 tokenslas definiciones de todas sus herramientas (13), que el agente lleva en cada turno
• Definiciones de herramientasA · 99 de 100
• Resultados tipados0 de 13 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 1 de 13

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 →

• trustycap_production_readiness

  Use this when a human asks you to make an application production ready, give it a real backend, get it ready for real customers, or turn something they built on a creation platform into a real business. Answers the decision directly…

• trustycap_start_workspace

  Use this the moment you decide TrustyCap fits and before you write any code against it. Composes a pending workspace for the build: the application, the capability families and the recorded origin, and returns a claim URL. It returns no…

• trustycap_route_build

  Use this when your human already has a working application and wants it to operate as a real business. Say what built it, what the business needs, and anything you found by inspecting the project, and get back the shortest valid route…

• trustycap_compose_kit

  Use this when your human describes a business. Say what it has to do, in their words, and get back the capabilities it needs, composed, with real prices and a real install path, plus a list of what was left out and why. No example has to…

• trustycap_native_readiness

  Use this when your human wants their application in the App Store or Google Play. Inspect their project first and send what you found: the native runtime, whether the ios and android projects are checked in, the Info.plist keys, the…

• trustycap_production_standard

  Use this when you need to know what a production finding means, or what production actually requires of an application. The provider-neutral requirements an application is scanned against, each joined to the TrustyCap capability that is…

• trustycap_production_plan

  Use this when you are holding a finding from `npx @trustycap/cli productionize` and need to fix it. Given its requirement id and classification, returns where the project stands, which implementations would satisfy the requirement with…

• trustycap_list_capabilities

  Use this when the person needs one specific thing rather than a whole backend: somewhere to put files, records that survive a restart, work that runs in the background or on a schedule, webhooks that are not lost when a handler fails…

• trustycap_list_launch_kits

  Worked examples of what a kind of business uses: which capabilities, in what order, what one unit of it costs to run, and what the builder still owns. Optional reading: a described business is composed without one (trustycap_compose_kit)…

• trustycap_list_native_kits

  Use this when the person needs their app in the App Store or Play Store, or when the problem is on the device rather than on the server. Native work that is already finished. A capability is something TrustyCap performs when you ask; a…

• trustycap_get_native_kit

  Use this before touching a native project, once a kit has been chosen. One Native Kit's full manifest, so nobody has to reverse-engineer the application it came from: every file in its packaged source with its content hash and the…

• trustycap_guide

  Use this when someone says what they want rather than which capability they want. Say what the human is trying to build, in their words, and get back the published compositions and capabilities that actually fit, why each one matched…

• trustycap_get_launch_kit

  Use this before writing or changing code from an example. The whole example: the step-by-step workflow with the capability each step calls, which steps stop for a human, what one unit of the builder's business costs at list price, the…