Build abstracts on Amorphous. An abstract can be anything.
Nothing to run from here
TrustyCap is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
13
tools declared
remote
at its publisher
—
calls last 7d
What it does
Production backend for AI-built apps: storage, data, jobs, webhooks, email, metering and billing.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http trustycap-mcp https://mcp.trustycap.com/mcp
# 2 — ask your agent for something these tools do
# trustycap_production_readiness, trustycap_start_workspace, trustycap_route_build and 10 more
TrustyCap costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TRAll 1 server
trustycap1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http trustycap-mcp https://mcp.trustycap.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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, what it costs, how it behaves when things fail, what repairs itself, how to undo it, and the eviden
No parameter schema on file.
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, until a person whose developer access is approved claims it. Say which creation platform built their ap
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | What your human calls the thing they built. |
| platform | string | no | The creation platform their application came from. One of: lovable, replit, base44, bolt, v0, claude_code, codex, cursor, windsurf, own_code. Omit if you genuinely do not know; do not guess. |
| intent | string | no | What the business needs, in your human's own words. Never their source code. |
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 sold again, what is genuinely missing, what TrustyCap is honestly not the answer to, which capabilities
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platform | string | no | The creation platform their application came from: lovable, replit, base44, bolt, v0, claude_code, codex, cursor, windsurf, own_code. |
| intent | string | no | What the business needs, in your human's own words. |
| framework | string | no | The framework you detected, if any. |
| has | array | no | Concerns the project already answers, from your own inspection. Use the concern ids from GET /v1/platforms. |
| findings | array | no | Requirement ids the production scan reported as not passing, e.g. TC-PROD-0041. Run npx @trustycap/cli productionize to get them. |
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 to compose anything that platform already supplies. Pass capability ids instead of a sentence to comp
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intent | string | yes | What the business has to do, in your human's own words. |
| platform | string | no | The creation platform their application came from. |
| capabilities | array | no | Capability ids or aliases to compose exactly, instead of matching on the sentence. |
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. npx @trustycap/cli native reads all of that for you. Returns, per Native Kit, which requirements a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intent | string | no | What the app has to do on the phone, in your human's words. |
| platform | string | no | The creation platform their application came from. |
| kits | array | no | Specific Native Kit ids, instead of matching on the sentence. |
| runtime | string | yes | capacitor, expo, react-native, or none. |
| ios | boolean | no | Whether an ios/ directory is checked in. |
| android | boolean | no | Whether an android/ directory is checked in. |
| info_plist_keys | array | no | — |
| android_manifest_keys | array | no | — |
| entitlements | array | no | — |
| min_sdk | integer | no | — |
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 such as TC-PROD-0041 from npx @trustycap/cli productionize, to see which properties a requirement
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requirement | string | no | A requirement id, e.g. TC-PROD-0041. Omit for the whole standard. |
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 not see), the TrustyCap remediation and the exact commands to run and verify, and when TrustyCap sho
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requirement | string | yes | The finding's requirement id, e.g. TC-PROD-0041 |
| classification | string | yes | The finding's classification |
| provider | string | no | The provider the scanner recognized, if any |
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 into structured data, money held until delivery is proven, an insurance claim checked before it goes
| Parameter | Type | Required | Notes |
|---|---|---|---|
| family | string | no | Optional family filter. Accepts the neutral name (vehicle, financing, documents, transactions, digital-life, exit-paths, finance-math) or the canonical id. |
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 contract is the default. An example is a starting point, never a finished product: the brand, the customer,
No parameter schema on file.
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 dependency pins, permissions, entitlements, plist keys and protected configuration that make it work, c
No parameter schema on file.
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 pin, every permission, entitlement, background mode and plist or manifest key with what breaks when
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Native Kit id, e.g. background-location |
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 build plan you can act on. Use this when someone says what they want rather than which capability the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intent | string | yes | What the builder said they want to build, in their own words. |
| launch_kit | string | no | Optional. The id of a published composition (GET /v1/launch-kits) to plan against directly, skipping the recommendation. |
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 contract classifies every surface as customizable, extensible, required, platform_managed or protected, so
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Composition id, e.g. vehicle-finance |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install TrustyCap or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 2.0.4 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest3bb593b84a9187a69e63cc787207f67b16f57553ece911d0d2ad99f892b40305
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| trustycap_production_readiness | no tags | |
| trustycap_start_workspace | state-write | state-write: declares readOnlyHint: false |
| trustycap_route_build | no tags | |
| trustycap_compose_kit | no tags | |
| trustycap_native_readiness | no tags | |
| trustycap_production_standard | no tags | |
| trustycap_production_plan | no tags | |
| trustycap_list_capabilities | no tags | |
| trustycap_list_launch_kits | no tags | |
| trustycap_list_native_kits | no tags | |
| trustycap_get_native_kit | no tags | |
| trustycap_guide | no tags | |
| trustycap_get_launch_kit | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest3bb593b84a9187a6
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.4.
2.0.4
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish TrustyCap can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.