ai.bobos/dispatcher
Bobos Dispatcher
Is the Bobos Dispatcher MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-30.
Run every client's AI from one console: workspaces, roles, MCP tools, approvals and spend.
needs auth probed 2026-11-15 · unchanged since 2026-10-30 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {
"message": "Access denied by Imunify360 bot-protection. IPs used for automation should be whitelisted"
}- Endpoint
- https://dispatcher.bobos.ai/mcp/v1/control (streamable-http)
- Host
- dispatcher.bobos.ai
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://dispatcher.bobos.ai/mcp/v1/control registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server dispatcher.bobos.ai, PKCE S256, grants authorization_code, refresh_token.
Scopes account:read account:write connections:read connections:write mcp_servers:read mcp_servers:write providers:read providers:write ledger:read ledger:write billing:read schedules:read schedules:write approvals:read approvals:reject roles:read roles:write agents:read agents:write skills:read.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://dispatcher.bobos.ai/docs/connect
- Registry
- active, updated 2026-10-28 · registry entry
Compare this server with others.
More servers
Servers that mention dispatcher.
- Frisian MCP (Django) com.frisian-mcp/django · alive
- MCP Near Me com.voicedispatcher/mcp-near-me · alive
- Execute amr-fleet-dispatcher-mcp io.github.Evozim/amr-fleet-dispatcher-mcp · timeout
- GenPark Priority Event Scheduler Queue io.github.alphaparkinc/genpark-priority-event-scheduler-queue-skill · install failed
- GenPark JSON-RPC Batch Pipelining Dispatcher io.github.alphaparkinc/genpark-json-rpc-batch-pipelining-dispatcher-skill · install failed
- GraphyLoop io.github.chadixearth/graphyloop · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.