Retired: install com.trustycap/trustycap is a remote MCP server that gives an AI agent 9 tools, among them trustycap_get_launch_kit, trustycap_get_native_kit, trustycap_guide. It answers at https://mcp.trustysweep.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Retired identity. TrustyCap is published as com.trustycap/trustycap. Install that.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
trustycap_get_launch_kit | Use this before writing or changing code against a 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 a Inputs: id |
trustycap_get_native_kit | Use this before touching a native project, once a kit has been chosen. 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 i Inputs: id |
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 Launch Kits and capabilities that actually fit, why each one matched, what one unit of Inputs: intent, launch_kit |
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, crede Inputs: family |
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. The Backend Launch K |
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 already finished. A capability is something TrustyCap performs when you ask; a Nati |
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 the project stands, which implementations would satisfy the requirement with thei Inputs: requirement, classification, provider |
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. Answers the decision directly: whethe |
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. The provider-neutral requirements an application is scanned against, each joined to the TrustyCap capability th Inputs: requirement |
Every block below points at https://mcp.trustysweep.com/mcp. Pick your client and copy.
claude mcp add --transport http retired-install-com-trustycap-tr https://mcp.trustysweep.com/mcp
{
"mcpServers": {
"retired-install-com-trustycap-tr": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.trustysweep.com/mcp"]
}
}
}{
"mcpServers": {
"retired-install-com-trustycap-tr": {
"url": "https://mcp.trustysweep.com/mcp"
}
}
}{
"servers": {
"retired-install-com-trustycap-tr": {
"type": "http",
"url": "https://mcp.trustysweep.com/mcp"
}
}
}{
"context_servers": {
"retired-install-com-trustycap-tr": {
"url": "https://mcp.trustysweep.com/mcp"
}
}
}{
"mcpServers": {
"retired-install-com-trustycap-tr": {
"serverUrl": "https://mcp.trustysweep.com/mcp"
}
}
}{
"mcpServers": {
"retired-install-com-trustycap-tr": {
"url": "https://mcp.trustysweep.com/mcp"
}
}
}name: Retired: install com.trustycap/trustycap
version: 0.0.1
schema: v1
mcpServers:
- name: Retired: install com.trustycap/trustycap
type: streamable-http
url: https://mcp.trustysweep.com/mcp{
"mcpServers": {
"retired-install-com-trustycap-tr": {
"httpUrl": "https://mcp.trustysweep.com/mcp"
}
}
}{
"mcpServers": {
"retired-install-com-trustycap-tr": {
"type": "http",
"url": "https://mcp.trustysweep.com/mcp"
}
}
}{
"mcpServers": {
"retired-install-com-trustycap-tr": {
"url": "https://mcp.trustysweep.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.trustysweep.com%2Fmcp&type=streamable_http&id=retired-install-com-trustycap-tr&name=Retired%3A%20install%20com.trustycap/trustycap
It answered our last check on 19 October 2026 in 348 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by trustysweep.com and served from mcp.trustysweep.com, the vendor's own domain: https://mcp.trustysweep.com/mcp.
9, as returned by the server's own tools/list on 11 September 2026: trustycap_get_launch_kit, trustycap_get_native_kit, trustycap_guide, trustycap_list_capabilities, trustycap_list_launch_kits, trustycap_list_native_kits, trustycap_production_plan, trustycap_production_readiness, and 1 more.
It answered our last check on 19 October 2026 in 348 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.trustysweep.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.trustysweep. Endpoint host: mcp.trustysweep.com. ARD identifier: urn:air:com.trustysweep:mcp:sweep.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.