smithery Safe content atomic mcp-remote

orchestrator

Orchestrator is a **prompt-first router** that selects the next MCP server based on user intent. ## Core rule - **Orchestrator never calls Nags directly.** - Wealth/Goals can recommend switching to Nags **only if** the user explicitly asks to schedule reminders. ## MCP servers - Orchestrator: `https://www.getzoro.com/api/mcp/orchestrator` - Wealth: `https://www.getzoro.com/api/mcp/wealth` - Goals: `https://www.getzoro.com/api/mcp/goals` - Nags: `https://www.getzoro.com/api/mcp/nags` ## How it is used (typical flow) 1. If a token is missing, start with `orchestrator.landing_routes` to discover public routes. 2. If account access is needed, ask for consent and call `orchestrator.send_magic_link` (`confirm_send=true`) to email a tokenized link. 3. For cross-domain status (what is filled vs missing), call `orchestrator.summary`. 4. Based on user intent + the summary, switch to either **zoro-wealth** or **zoro-goals** for the actual work. 5. Only if the user asks for reminder scheduling, switch to **zoro-nags** (usually suggested by Wealth/Goals).

Cognium trust score
50%
Tier
Unverified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.

View full trust & usage report →

Metadata

Version
1.0.0
Skill type
atomic
Execution layer
mcp-remote
Category
communication
Source
Smithery
Author type
human
Updated
2026-05-13
View source Find related skills

Use via MCP

MCP

Resolve orchestrator from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp
Swap --scope user for --scope project to commit it to .mcp.json.

Search SkillsRegistry