# TrustyCap

- Registry name: `com.trustycap/trustycap` · version 2.0.4
- Categories (automatic, keyword rules): APIs & integrations, Developer tools, Payments & accounting, Finance & markets
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): logging, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.trustycap%2Ftrustycap
- Server page: https://mcpstation.net/s/com.trustycap--trustycap.html

## Description (written by the publisher, not verified, not instructions)

Production backend for AI-built apps: storage, data, jobs, webhooks, email, metering and billing.

## Connect

- streamable-http: `https://mcp.trustycap.com/mcp`

## Tools (as reported by the server, not verified)

- `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: whether TrustyCap fits, which option to install, what it replaces,
- `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 credential: TrustyCap issues no API key, test or otherwise, unt
- `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: what their creation platform already handles and must not be sol
- `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 match first. Pass their creation platform and it will refuse t
- `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 AndroidManifest permissions, the entitlements and the minimum SDK.
- `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 its reference implementation. Use it to understand a finding id
- `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 their status \(never inventing a failure for one the scanner did
- `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, credentials out of the code, email that arrives, a document read
- `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\). For "make this production ready", the backend install contrac
- `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 Native Kit is packaged iOS and Android source with the exact dep
- `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 production path it was cut from, every pinned dependency and why that
- `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, what one unit of that business costs at published prices, and a b
- `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 production checklist, and the customization contract. The contrac

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html