net.chorushq/chorus

Chorus

Is the Chorus MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-11.

Run ad campaigns on Meta, Google Ads and LinkedIn from your assistant. Spend waits for your OK.

needs auth probed 2026-11-15 · unchanged since 2026-11-11 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"error": "unauthorized", "error_description": "Sign in to Chorus to use this connector."}

Endpoint: https://mcp.chorushq.net/mcp (streamable-http)
Host: mcp.chorushq.net
Getting access: OAuth without dynamic client registration. Ask the publisher for a client id first; with it, a client can run the consent.
Authorization server www.chorushq.net, PKCE S256, grants authorization_code, refresh_token.
Scopes ads.read ads.write chorus.ai.
Read from the server's public OAuth metadata, without a token. Method.
Website: https://www.chorushq.net/mcp
Registry: active, updated 2026-10-20 · registry entry
Changes: 3 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.

More servers

Servers that mention chorus.

We add a row when the result changes. A server with no change keeps its last row.

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

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.