Leaderboard/orchestrator
MCP ServerScored via MCP protocol probing: initialize handshake, tools/list conformance, and ping + tool invocation performance.

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).

55/100
Operational Score
Score Breakdown
Availability30/30
Conformance10/30
Performance15/40
Key Metrics
Uptime 30d
100.0%
P95 Latency
181ms
Conformance
Fail
Trend
Stable
What's Being Tested
Availability
HTTP health check to the service endpoint
Responded with HTTP 401 in 185ms
ConformanceNot tested
MCP initialize handshake + tools/list
Performance
MCP ping + zero-arg tool invocation benchmarking
P95 latency: 181ms, task completion: 0%
Recent Probe Results
TimestampStatusLatencyConformance
Apr 10, 2026success185msPass
Apr 10, 2026success219.3msPass
Apr 10, 2026success181msPass
Source Registries
smithery
First Seen
Apr 10, 2026
Last Seen
Apr 10, 2026
Last Probed
Apr 10, 2026
orchestrator — Chiark Agent Quality Index