io.hibira/mcp
Hibira
Is the Hibira MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Create and manage Hibira realtime apps (Pusher protocol compatible) from your AI agent.
needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"authentication required: sign in with OAuth or send a Hibira access token as a Bearer token"}
- Endpoint
- https://hibira.io/mcp (streamable-http)
- Host
- hibira.io
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://hibira.io/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server hibira.io, PKCE S256, grants authorization_code, refresh_token.
Scopes read write.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://hibira.io/mcp-server
- Registry
- active, updated 2026-10-24 · registry entry
Compare this server with others.
More servers
Servers that mention hibira.
- Gaya io.hibira/gaya · needs auth
- Hibira Live Chat io.hibira/live-chat · needs auth
- Approval gate for databases io.hibira/mcp-approval-gate · not found
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.