RMCP.DEV
← Registry

General Tools

trustycap.com

TrustyCap helps users discover business capabilities, assemble launch kits, and receive step-by-step plans with cost breakdowns and customization options.

2 endpoints10 known toolsFirst detected September 3, 2026Last detected September 3, 2026

ENDPOINT 1

https://mcp.trustycap.com/mcp

No auth detected

MCP server metadata

Name
trustycap
Version
2.0.0
Capabilities
toolsresourcespromptslogging
Server 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.

Known tools 4

trustycap_list_capabilities

Discover what TrustyCap can do.

Inferred read-only
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.

Inferred read-only
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.

Inferred read-only
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.

Inferred read-only

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.

ENDPOINT 2

https://mcp.trustysweep.com/mcp

No auth detected

MCP server metadata

Name
trustycap
Version
2.0.0
Capabilities
toolsresourcespromptslogging
Server 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.

Known tools 6

trustycap_list_capabilities

Discover what TrustyCap can do.

Inferred read-only
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.

Inferred read-only
trustycap_list_native_kits

Native work that is already finished.

Inferred read-only
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.

Inferred read-only
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.

Inferred read-only
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.

Inferred read-only

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.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.