app.heza/heza

Heza

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

Bring-your-own-AI fitness coach: your AI logs and reads your food, lifting, runs, sleep and weight.

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

Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"No authorization provided"}

Endpoint: https://my.heza.app/api/mcp (streamable-http)
Host: my.heza.app
Getting access: OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://my.heza.app/api/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 my.heza.app, PKCE S256, grants authorization_code, refresh_token.
Scopes forge.
Read from the server's public OAuth metadata, without a token. Method.
Website: https://heza.app/docs
Registry: active, updated 2026-11-12 · registry entry

More servers

Servers that mention fitness or lifting.

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.