MCP servercom.trustycap/trustycap
Production backend for AI-built apps: storage, data, jobs, webhooks, email, metering and billing.
Overview
Score?
UNRATED 0.646
of what a free look can see, on 25 looks
Looks
31
last 13 hr ago
Tools
13
changed 1 day ago
More info
URL
mcp.trustycap.com/mcp
streamable-http
Says it is
trustycap 2.0.4
protocol 2025-06-18
In the record since
29 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.646 · highest on record 0.8561
Toolsfrom sha256:edfb6a77fb…8af5e0 · +0 −0 1 day ago
| Tool | Schema |
|---|---|
| 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, pl |
input · no output |
| 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 u |
input · no output |
| 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 |
input · no output |
| 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 |
input · no output |
| 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 sche |
input · no output |
| 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 |
input · no output |
| 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 cap |
input · no output |
| 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 andro |
input · no output |
| 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, w |
input · no output |
| 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 |
input · no output |
| 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 |
input · no output |
| 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 inspect |
input · no output |
| 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 |
input · no output |
Verify it yourself
npx teppi-check https://mcp.trustycap.com/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1RE4SA4RNB94MJCVKZPQ200