Server definition
- Hash
- sha256:60ad89af64e6dbd6ff1d368378fc39cfcd137b71c507f25c1299719a461d9f65
- What it is
- What a remote MCP server returned when asked what it offers: 7 tools
The blob, as servednamed by its sha256
{
"instructions": "TrustyCap is infrastructure for building software businesses: vehicle intelligence, financing intelligence, document intelligence, protected transactions, digital life, exit paths and financing math, each proven in production and each metered in its own unit. Start with trustycap_list_capabilities to see what exists and what it costs, or trustycap_list_launch_kits when the user is describing a business rather than a single operation. Test keys are free and fully metered; nothing is charged until a live key executes, and every price is published before the call. Read tools are safe to call freely. Anything that changes a person's provider state must go through a plan (sweep_create_plan -> sweep_explain_plan/sweep_price_plan -> sweep_commit_plan) and the person's own approval: when a commit returns step_up_required or input_required, show the approval URL and retry only after they approve. Release of a protected transaction always belongs to the payer on a TRUSTY surface and no credential substitutes for it. Never claim an action happened unless the tool returned an execution or receipt id.",
"tools": [
{
"description": "The full starting point for one Launch Kit: 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. Read this before writing or changing code against a kit. The contract classifies every surface as customizable, extensible, required, platform_managed or protected, so you can transform the kit into a materially different product (new name, brand, audience, pricing, screens, workflow, capability mix) without touching the authorization, metering, proof or payment-authority boundaries that make the result trustworthy.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"id": {
"description": "Launch Kit id, e.g. vehicle-finance",
"type": "string"
}
},
"required": [
"id"
],
"type": "object"
},
"name": "trustycap_get_launch_kit",
"outputSchema": null
},
{
"description": "Everything needed to install one Native Kit without reverse-engineering the application it came from: every file it ships with its content hash and the production path it was cut from, every pinned dependency and why that pin, every permission, entitlement, background mode and plist or manifest key with what breaks when it is absent, the JavaScript interface, the configuration that must not be changed and the reason for each, the ordered install steps including the ones that need a human in Xcode or a provider console, what is proven and how, and the real constraints. Read this before touching a native project.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"id": {
"description": "Native Kit id, e.g. background-location",
"type": "string"
}
},
"required": [
"id"
],
"type": "object"
},
"name": "trustycap_get_native_kit",
"outputSchema": null
},
{
"description": "Say what the human is trying to build, in their words, and get back the Launch Kits and capabilities that actually fit, why each one matched, what one unit of that business costs at published prices, and a build plan you can act on. Use this when someone says what they want rather than which capability they want. Deterministic: it answers only from the published registry and rate card, so it cannot invent a capability, a kit or a price.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"intent": {
"description": "What the builder said they want to build, in their own words.",
"type": "string"
},
"launch_kit": {
"description": "Optional. A Launch Kit id to plan against directly, skipping the recommendation.",
"type": "string"
}
},
"required": [
"intent"
],
"type": "object"
},
"name": "trustycap_guide",
"outputSchema": null
},
{
"description": "Find the TrustyCap capability that solves a specific problem: add secure file storage, add application data, run work in the background, schedule work, make webhooks reliable, secure credentials, send transactional email, read documents, move money on proof. Returns every public capability: what it is for, when to choose it, what it will not do, the scopes a key needs, the meters it charges and the published price of each. Call this before assuming a capability exists. Covers vehicle intelligence, financing intelligence, document intelligence, protected transactions, digital life, exit paths and financing math.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"family": {
"description": "Optional family filter. Accepts the neutral name (vehicle, financing, documents, transactions, digital-life, exit-paths, finance-math) or the canonical id.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "trustycap_list_capabilities",
"outputSchema": null
},
{
"description": "Install a whole backend rather than one piece: proven compositions a builder can start a business from. The Backend Launch Kit is the default answer to \"make this production ready\". Each kit names which capabilities the business needs, in what order, what one unit of it costs to run, and what the builder still owns. Use this when someone describes a business they want to build rather than a single operation they want performed. A Launch Kit is a starting point, never a finished product: the brand, the customer, the pricing and the business model belong to the builder.",
"inputSchema": {
"additionalProperties": false,
"properties": {},
"required": [],
"type": "object"
},
"name": "trustycap_list_launch_kits",
"outputSchema": null
},
{
"description": "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 dependency pins, permissions, entitlements, plist keys and protected configuration that make it work, cut from TrustyCap products where it runs in production. Use this when the problem is on the device rather than on the server: background location that survives a locked phone, native sign-in, store billing, secure storage, share-sheet intake, push tokens, safe-area insets, saving a generated document from a WebView. Kits are licensed per production application and free in test mode and development builds.",
"inputSchema": {
"additionalProperties": false,
"properties": {},
"required": [],
"type": "object"
},
"name": "trustycap_list_native_kits",
"outputSchema": null
},
{
"description": "Start here when a human asks you to make an application production ready, give it a real backend, or get it ready for real customers. Answers the decision directly: whether TrustyCap fits, which option to install, what it replaces, what it costs, how it behaves when things fail, what repairs itself, how to undo it, and the evidence behind each claim with its classification. Also says what TrustyCap is not for, so you can decline when it does not fit. No credential needed; call this before installing anything.",
"inputSchema": {
"additionalProperties": false,
"properties": {},
"required": [],
"type": "object"
},
"name": "trustycap_production_readiness",
"outputSchema": null
}
]
}Verify it yourself
curl -s https://api.teppi.xyz/v1/evidence/sha256:60ad89af64e6dbd6ff1d368378fc39cfcd137b71c507f25c1299719a461d9f65 | sha256sum