io.github.hey-juno/juno
Juno AI Customer Research
Is the Juno AI Customer Research MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
AI-moderated qualitative customer interviews, study authoring, participant links, and CSV exports.
needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized"}- Endpoint
- https://api.heyjuno.co/v1/mcp/ (streamable-http)
- Host
- api.heyjuno.co
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.heyjuno.co/v1/mcp/ registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server api.heyjuno.co, PKCE S256, grants authorization_code, refresh_token.
Scopes export:read links:read links:write studies:golive studies:read studies:write.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/hey-juno/juno-agent-toolkit
- Website
- https://www.heyjuno.co/documents/mcp/quickstart
- Registry
- active, updated 2026-10-20 · registry entry
Compare this server with others.
More servers
Servers that mention juno.
- ai.smithery/JunoJunHyun-festival-finder-mcp · not found
- Juno Open Health Tools io.github.MarshallBear1/juno-open-health-tools · alive
- Agenda Rio io.github.junoventures/agenda-rio-br · alive
- Bela Vista io.github.junoventures/belavista-sampa-br · alive
- Olé Futebol io.github.junoventures/olefutebol-com-br · no DNS
- Aclimação io.github.junoventures/aclimacao-sampa-br · no DNS
- Agenda SP io.github.junoventures/agenda-sampa-br · alive
- Bogeyland io.github.junoventures/bogeyland-golf · 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.