dev.uup/mcp
You Up?
Is the You Up? MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Uptime monitoring from your AI assistant: what is down, Incidents, and your Monitors.
needs auth probed 2026-11-14 · HTTP 401
Streamable HTTP error: Error POSTing to endpoint: {"error":{"code":"unauthenticated","message":"Send a working API token as `Authorization: Bearer uup_api_…`. M- Endpoint
- https://api.uup.dev/mcp (streamable-http)
- Host
- api.uup.dev
- Getting access
- The server answers HTTP 401 with no WWW-Authenticate header and no OAuth metadata, so the publisher's documentation is the only guide.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://docs.uup.dev/api/mcp/
- Registry
- active, updated 2026-11-13 · registry entry
Compare this server with others.
More servers
Servers that mention monitoring or incidents.
- Agentic News ai.agentic-news/mcp · needs auth
- ai.getvda/kafka-and-postgres-monitoring-stack · newer protocol
- ai.openhelm/monitoring · needs auth
- Revelara ai.revelara/mcp · needs auth
- Safeship app.safeship/mcp · needs auth
- co.axiom/mcp · needs auth
- co.vantaj/mcp-server · alive
- AgentLinkOps com.agentlinkops/agentlinkops · 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 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.