app.liveintently/respite
Respite Screen Time
Is the Respite Screen Time MCP server down? No. It is up and needs auth (HTTP 403), probed 2026-11-13.
Your phone and browser screen time from the Respite app: ask, set stricter limits, start focus.
needs auth probed 2026-11-15 · unchanged since 2026-11-13 · HTTP 403
Streamable HTTP error: Error POSTing to endpoint: <!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title><meta http-equiv="Content-Type" content
- Endpoint
- https://respite-api.liveintently.app/mcp (streamable-http)
- Host
- respite-api.liveintently.app
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://respite-api.liveintently.app/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server respite-api.liveintently.app, PKCE S256, grants authorization_code, refresh_token.
Scopes respite:read respite:limits respite:interventions respite:rules.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://respite.liveintently.app/ai/
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention screen or time.
- ac.snag/snag · needs auth
- aTars MCP ai.aarna/atars-mcp · server error
- AlphaCreek SEC Filings MCP ai.alphacreek/alphacreek-mcp · alive
- Teamwork ai.b77/teamwork · needs auth
- Time ai.b77/time · needs auth
- BeatBandit MCP ai.beatbandit/beatbandit · needs auth
- BetterPost ai.betterpost/server · alive
- ai.boundaryai/boundaryai · needs auth
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 403 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.