Retired: install com.trustycap/trustycap

The tools are organized around distinct phases (discovery, readiness, routing, composition, workspace), and descriptions explicitly cross-reference when to use one over another. However, compose_kit, guide, route_build, and start_workspace all occupy a similar 'what should I build/install' space requiring careful reading to pick correctly.

All names share the trustycap_ prefix and lowercase snake_case, so the set looks uniform at a glance, but the suffixes mix verb_noun forms (list_capabilities, compose_kit, start_workspace) with noun-only forms (guide, native_readiness, production_plan, production_standard). This split makes the naming pattern only partially predictable.

Thirteen tools is within a reasonable range for a platform covering capabilities, launch kits, native kits, production readiness, and workspace setup. The count is justified, though a few readiness/plan/standard tools are close in function and could arguably be consolidated.

The set covers the full journey from discovery (list/guide), through fit assessment and readiness scanning, to routing, kit selection, and starting a workspace with a claim URL. Minor gaps exist around post-workspace lifecycle (status, updates, deletion), but those appear intentionally handled outside the MCP surface.