INDIVIDUAL MCP TOOL

trustycap_native_readiness

Use this when your human wants their application in the App Store or Google Play.

trustycap.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.trustycap.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for trustycap_native_readiness and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

trustycap.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.trustycap]
url = "https://mcp.trustycap.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "trustycap": {
      "type": "http",
      "url": "https://mcp.trustycap.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: trustycap
Remote MCP URL: https://mcp.trustycap.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "trustycap": {
      "url": "https://mcp.trustycap.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "trustycap": {
      "type": "http",
      "url": "https://mcp.trustycap.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "trustycap",
  "transport": "streamable-http",
  "url": "https://mcp.trustycap.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

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.
trustycap_start_workspace — Use this the moment you decide TrustyCap fits and before you write any code against it.
trustycap_route_build — Use this when your human already has a working application and wants it to operate as a real business.
trustycap_compose_kit — Use this when what your human is building is not one of the published Launch Kits.
trustycap_production_standard — Use this when you need to know what a production finding means, or what production actually requires of an AI-built application.
trustycap_production_plan — Use this when you are holding a finding from `npx @trustycap/cli productionize` and need to fix it.
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 into structured data, money held until delivery is proven, an insurance claim checked before it goes out, or a vehicle, loan or property fact resolved.
trustycap_list_launch_kits — Use this when someone describes a business they want to build rather than a single operation they want performed, and needs a whole backend rather than one piece: proven compositions a builder can start a business from.