mcpcost

io.github.danielsemecky/glimpze

Glimpze

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

Review Glimpze website chats, video-call history and recordings, and manage support workflows.

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

Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":0,"error":{"code":-32600,"message":"Missing credential. Send Authorization: Bearer <your
Endpoint
https://api.glimpze.io/functions/v1/mcp (streamable-http)
Host
api.glimpze.io
Getting access
OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.glimpze.io/functions/v1/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 fdituzopgqvgdwcdhlkz.supabase.co, PKCE S256, grants authorization_code, refresh_token.
Scopes email.
Read from the server's public OAuth metadata, without a token. Method.
Website
https://www.glimpze.io/docs/mcp
Registry
active, updated 2026-11-09 · registry entry

Compare this server with others.

More servers

Servers that mention recordings or workflows.

Badge for the README

mcpcost: needs auth

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

Atom feed

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

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.