Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is cronalert free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does cronalert have?

12 tools: get_monitor, get_check_results, get_monitor_incidents, create_monitor, update_monitor, add_incident_update, import_monitors, list_incidents, ….

Is cronalert safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp http-sse · checked 1h ago

cronalert

https://cronalert.com

Registry code: fa2c2e0c511afe93

api record

Manage CronAlert uptime monitors, check results, and handle incidents.

from a public catalogue that lists it, not from the operator

endpoint: https://cronalert.com/mcp
protocol: http-sse ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is cronalert live?: Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is cronalert free to use?: Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does cronalert have?: 12 tools: get_monitor, get_check_results, get_monitor_incidents, create_monitor, update_monitor, add_incident_update, import_monitors, list_incidents, ….
Is cronalert safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

100%

90 days 100%· all time 100%

latency

874ms

last good check

priced tools

of 12 tools

_ answered our checks, 90 days 409 checks · signed record

2026-10-12 10:10 degraded → live
2026-09-27 07:01 unknown → live

_ what it is for

topic: infrastructure & devops monitoring & observability
used for: create an uptime monitor for a url
get monitor check results
list active incidents
post an incident status update
import monitors from another service
takes → gives: data → data
tools: 7 reads5 changes data

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 12 tools

9 auth-required 3 never probed 9 of 12 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

create_monitor changes data auth-required never probed

Create a new uptime monitor. Supports HTTP status checks, keyword matching, regex matching, content change detection, and content staleness alerts (Pro+).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name",
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "format": "uri"
    },
    "name": {
      "type": "string"
    },
    "method": {
      "enum": [
        "GET",
        "POST",
        "PUT",
        "PATCH",
        "DELETE",
        "HEAD"
      ],
      "type": "string",
      "default": "GET"
    },
    "keyword": {
      "type": "string",
      "description": "Value depends on keywordMatchType: keyword text for contains/not_contains, regex pattern for regex_match/regex_not_match, number of days for content_stale, unused for content_changed"
    },
    "checkInterval": {
      "type": "number",
      "default": 180
    },
    "keywordMatchType": {
      "enum": [
        "contains",
        "not_contains",
        "regex_match",
        "regex_not_match",
        "content_changed",
        "content_stale"
      ],
      "type": "string",
      "description": "Content check mode: contains/not_contains for keyword, regex_match/regex_not_match for regex, content_changed for hash-based change detection, content_stale for staleness alerts"
    },
    "expectedStatusCode": {
      "type": "number",
      "default": 200
    }
  }
}

arguments 53 lines

update_monitor changes data auth-required never probed

Update an existing monitor's configuration (name, URL, interval, method, content checking, etc.).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "url": {
      "type": "string",
      "format": "uri"
    },
    "name": {
      "type": "string"
    },
    "method": {
      "enum": [
        "GET",
        "POST",
        "PUT",
        "PATCH",
        "DELETE",
        "HEAD"
      ],
      "type": "string"
    },
    "paused": {
      "type": "boolean"
    },
    "keyword": {
      "type": "string",
      "description": "Value depends on keywordMatchType: keyword text, regex pattern, number of days, or unused"
    },
    "checkInterval": {
      "type": "number"
    },
    "keywordMatchType": {
      "enum": [
        "contains",
        "not_contains",
        "regex_match",
        "regex_not_match",
        "content_changed",
        "content_stale"
      ],
      "type": "string"
    },
    "expectedStatusCode": {
      "type": "number"
    }
  }
}

arguments 54 lines

add_incident_update changes data auth-required never probed

Post a status update on an active incident. Updates appear on the public status page.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "incidentId",
    "status",
    "message"
  ],
  "properties": {
    "status": {
      "enum": [
        "investigating",
        "identified",
        "monitoring",
        "update",
        "resolved"
      ],
      "type": "string"
    },
    "message": {
      "type": "string"
    },
    "incidentId": {
      "type": "string"
    }
  }
}

arguments 27 lines

import_monitors changes data auth-required never probed

Import monitors from another monitoring service. Supports UptimeRobot, Pingdom, Better Stack, StatusCake, Checkly, Oh Dear, Cronitor, Healthchecks.io, Dead Man's Snitch, Datadog, CronAlert JSON, and CSV formats.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "format",
    "data"
  ],
  "properties": {
    "data": {
      "type": "string",
      "description": "Raw JSON or CSV string exported from the source service"
    },
    "format": {
      "enum": [
        "uptimerobot",
        "pingdom",
        "betterstack",
        "statuscake",
        "checkly",
        "ohdear",
        "cronitor",
        "healthchecks",
        "deadmanssnitch",
        "datadog",
        "cronalert",
        "csv"
      ],
      "type": "string",
      "description": "Source format of the monitoring data"
    }
  }
}

arguments 32 lines

list_incidents reads auth-required 16h ago
List all active incidents across all monitors.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines
delete_monitor changes data auth-required never probed
Permanently delete a monitor and all its check history. This cannot be undone.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "id": { "type": "string" } } }
arguments 12 lines

get_incident_updates reads auth-required never probed

Get status updates for a specific incident.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "incidentId"
  ],
  "properties": {
    "incidentId": {
      "type": "string"
    }
  }
}

arguments 12 lines

list_monitors reads auth-required 16h ago

List all uptime monitors. Optionally filter by status (up, down, unknown) and paginate.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "page": {
      "type": "number"
    },
    "limit": {
      "type": "number",
      "maximum": 100
    },
    "status": {
      "enum": [
        "up",
        "down",
        "unknown"
      ],
      "type": "string"
    }
  }
}

arguments 21 lines

list_status_pages reads auth-required 16h ago
List all public status pages configured for your account.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

get_monitor reads unknown 12h ago

Get detailed information about a specific monitor including its current status.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    }
  }
}

arguments 12 lines

get_check_results reads unknown 12h ago

Get recent check results for a monitor, including response times, status codes, and uptime percentage.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "page": {
      "type": "number"
    },
    "limit": {
      "type": "number",
      "maximum": 100
    }
  }
}

arguments 19 lines

get_monitor_incidents reads unknown 12h ago

Get incidents for a specific monitor — periods when the monitor was down.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "page": {
      "type": "number"
    },
    "limit": {
      "type": "number",
      "maximum": 100
    }
  }
}

arguments 19 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id fa2c2e0c511afe93.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/fa2c2e0c511afe93/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/fa2c2e0c511afe93/badge.svg)](https://brick.blue/agent/fa2c2e0c511afe93?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.