TrustyCap

Name: TrustyCap
Author: com.trustycap

MCP serverMCP

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

Until 2026-09-26 this record combined several servers published from one repository. The others now have records of their own: TrustyCap (formerly Trusty Sweep). Checks from before that date include them.

by com.trustycaphomepage ↗v2.0.4

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"trustycap","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability138/143 checks ok

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	230 ms	server trustycap 2.0.4 · protocol 2025-06-18 · 13 tools
12 h ago	mcp initialize	ok	200	61 ms	server trustycap 2.0.4 · protocol 2025-06-18 · 13 tools
18 h ago	mcp initialize	ok	200	119 ms	server trustycap 2.0.4 · protocol 2025-06-18 · 13 tools
25 h ago	mcp initialize	ok	200	67 ms	server trustycap 2.0.4 · protocol 2025-06-18 · 13 tools
31 h ago	mcp initialize	ok	200	134 ms	server trustycap 2.0.4 · protocol 2025-06-18 · 13 tools
2 d ago	mcp initialize	ok	200	107 ms	server trustycap 2.0.4 · protocol 2025-06-18 · 13 tools
2 d ago	mcp initialize	ok	200	89 ms	server trustycap 2.0.4 · protocol 2025-06-18 · 13 tools
2 d ago	mcp initialize	ok	200	75 ms	server trustycap 2.0.4 · protocol 2025-06-18 · 13 tools
2 d ago	mcp initialize	ok	200	110 ms	server trustycap 2.0.4 · protocol 2025-06-18 · 13 tools
3 d ago	mcp initialize	ok	200	100 ms	server trustycap 2.0.4 · protocol 2025-06-18 · 13 tools

Tools observed via MCP handshake

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
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 capabil
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
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 r
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, wheth
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 app
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 t
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 bac
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
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 alr
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
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 publis
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

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.trustycap/trustycap

first seen 1 mo ago · fetched 14 h agoopen ↗

Field history (12 recent events)

13 d ago · declared · publisherName → "com.trustycap"
13 d ago · declared · summary → "Production backend for AI-built apps: storage, data, jobs, webhooks, email, metering and billing."
13 d ago · declared · name → "TrustyCap"
13 d ago · declared · description → "Production backend for AI-built apps: storage, data, jobs, webhooks, email, metering and billing."
13 d ago · declared · version → "2.0.4"
13 d ago · declared · repoUrl → null
19 d ago · declared · version → "1.2.0"
19 d ago · declared · publisherName → "com.trustysweep"
19 d ago · declared · summary → "Deprecated first registry identity of TrustyCap. Install com.trustycap/trustycap instead."
19 d ago · declared · description → "Deprecated first registry identity of TrustyCap. Install com.trustycap/trustycap instead."
19 d ago · declared · name → "TrustyCap (formerly Trusty Sweep)"
23 d ago · declared · name → "TrustyCap"

TrustyCap

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from