mcpcost

com.cronobserver/mcp

CronObserver

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

Know when cron jobs and AI agents stop running: monitors, check-ins, incidents and runbooks.

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

Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32000,"message":"Missing Authorization: Bearer <CronObserver API key>"},"id"
Endpoint
https://cronobserver.com/mcp (streamable-http)
Host
cronobserver.com
Getting access
A key or token from the publisher, sent in the Authorization header (Bearer). The server publishes no OAuth metadata. Store the key once: npx mcpcost auth https://cronobserver.com/mcp --header "Authorization: Bearer …".
Read from the server's public OAuth metadata, without a token. Method.
Website
https://cronobserver.com/docs?utm_source=mcp-registry&utm_medium=listing&utm_campaign=growth-2026-11
Registry
active, updated 2026-11-12 · registry entry

Compare this server with others.

More servers

Servers that mention incidents or monitors.

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.