Connected MCP tools
Companion's sovereign-sync --mode mcp serves stdio tools. Select the existing
host with --socket or SOVEREIGN_SYNC_SOCKET. Registration never starts a
host or creates an independent P2P identity; unavailable host means unavailable.
| Tool | Request and result boundary |
|---|---|
sync-status | Optional domain annotates the selected host JSON; not convergence |
sync-peers | Selected host peer/transport snapshot; not enrollment |
sync-push | Explicit domain, optional unchanged signed_request; intent persisted before one POST |
sync-push-receipt | Original request_id, looked up on the same host |
A new push uses the named project's enrolled signer. Generic syncable domains
require exactly one registered project to choose that signer; resolve ambiguity.
Read durable intent and uncertainty
before replay. The source rejects unsupported --prefix-tools and
UAR_SKILL_SERVICE_URL passthrough; do not advertise tool aliases or an
undeclared extra tool set. Use Companion registration.
Ownership and evidence
These routes remain useful after relocation. The current recovered Companion
source (docs/installation.md, docs/control-api.md) has no public remote or
certified release yet. Source inspection is not installed or peer acceptance;
final source/artifact identities and publication links remain release-owned.
Use local KBD without the optional extension, and the service operations guide for pack/Companion ownership. The integration contract is a one-way seam. Relocation history is a decision record, not a Companion repository URL.