Servidor MCP de TrustyCap

• Nome no registrocom.trustycap/trustycapverificado no registro MCP

O nome no registro fica sob trustycap.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-10-25
• Ferramentas13
• O servidor se chamatrustycap
• Versão do servidor2.0.4
• Versão do protocolo2025-06-18

Em 2026-10-25 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 749 ms.

• Ainda não avaliamos se as ferramentas fazem o trabalho do produto.
• Verificado em 2 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 2 até agora
• Respondeumedindo2 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta1217 ms
• Espaço no contexto do agente≈ 3.536 tokensas definições de todas as ferramentas (13), que o agente carrega a cada turno
• Definições das ferramentasA · 99 de 100
• Resultados tipados0 de 13 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 1 de 13

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (30%), se faz o trabalho do produto (25%), definições (20%), contexto (10%) e uso (15%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e 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…