INDIVIDUAL MCP TOOL

trustycap_guide

Describe a business or an operation in plain language 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.

trustycap.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.trustysweep.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for trustycap_guide 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.trustysweep.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: trustycap
Remote MCP URL: https://mcp.trustysweep.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.trustysweep.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

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

MCP Inspector

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

Related tools

trustycap_list_capabilities — Discover what TrustyCap can do.
trustycap_list_launch_kits — Proven compositions a builder can start a business from: which capabilities the business needs, in what order, what one unit of it costs to run, and what the builder still owns.
trustycap_list_native_kits — Native work that is already finished.
trustycap_get_native_kit — 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.
trustycap_get_launch_kit — 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.