uptybots
Registry code: bd7e1142fd84ad88
Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.uptybots.com/mcp
- protocol
- streamable-http ·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 uptybots live?
- Yes — it answered the hub's last check (checked 7h ago). It answered 99% of checks over the last 30 days.
- Is uptybots 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 uptybots have?
- 15 tools: get_stats_daily, get_stats_hourly, get_incidents, create_http_monitor, create_ping_monitor, create_port_monitor, create_ssl_monitor, create_domain_monitor, ….
- Is uptybots 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.
90 days 99%· all time 99%
last good check
of 15 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- create http or api uptime monitors
- monitor ssl certificate and domain expiry
- get downtime incidents
- get uptime and response time stats
- takes → gives
- text, data → data
- tools
- 6 reads9 changes data
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.
through this hub
successful
what callers paid
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.
get_stats_daily reads auth-required 30h ago
Response time and uptime for one monitor aggregated per day, with min, max, average and p95. This is the tool for reports and trends over weeks or months, and for comparing one monitor against another over the same window. When a single day looks wrong, zoom into it with get_stats_hourly.
{ "type": "object", "required": [ "monitorId" ], "properties": { "page": { "type": "integer", "minimum": 1, "description": "Page number, 1-based. Defaults to 1." }, "dateTo": { "type": "string", "description": "Last day to include, as YYYY-MM-DD. Defaults to today." }, "dateFrom": { "type": "string", "description": "First day to include, as YYYY-MM-DD. Defaults to the start of available history." }, "monitorId": { "type": "integer", "minimum": 1, "description": "Monitor id, as returned by list_monitors." } }, "additionalProperties": false }arguments 27 linesget_stats_hourly reads auth-required 30h ago
Response time and uptime for one monitor broken down by hour, with min, max, average and p95 per bucket. Use it to see the shape of a problem: whether a service degrades before it fails, whether outages cluster at a particular time of day, or how long a single incident really lasted. Best over hours or days; for weeks and months use get_stats_daily instead, which returns far fewer rows.
{ "type": "object", "required": [ "monitorId" ], "properties": { "page": { "type": "integer", "minimum": 1, "description": "Page number, 1-based. Defaults to 1." }, "dateTo": { "type": "string", "description": "Last day to include, as YYYY-MM-DD. Defaults to today." }, "dateFrom": { "type": "string", "description": "First day to include, as YYYY-MM-DD. Defaults to the start of available history." }, "monitorId": { "type": "integer", "minimum": 1, "description": "Monitor id, as returned by list_monitors." } }, "additionalProperties": false }arguments 27 linesget_incidents reads auth-required 11h ago
Read the downtime history of one monitor: when each outage began, when it ended, how long it lasted and what the failure actually was - HTTP status, error text, and which probe saw it. This is the tool for "what happened" and "how often does this break". For the shape of response times around an outage, follow up with get_stats_hourly.
{ "type": "object", "required": [ "monitorId" ], "properties": { "page": { "type": "integer", "minimum": 1, "description": "Page number, 1-based. Defaults to 1." }, "monitorId": { "type": "integer", "minimum": 1, "description": "Monitor id, as returned by list_monitors." } }, "additionalProperties": false }arguments 19 linescreate_http_monitor changes data auth-required never probed
Watch a web page or endpoint over HTTP/HTTPS and treat an unexpected status code, a timeout or a connection failure as downtime. This is the right type for anything a browser would open. Choose create_api_monitor instead when the response body matters as well as the status code. Checks run from probes in several countries. Call list_monitors first so you do not create a duplicate of an existing url.
{ "type": "object", "required": [ "name", "url" ], "properties": { "url": { "type": "string", "description": "Full URL including scheme, for example https://example.com/health. A bare hostname is not accepted here - use create_ping_monitor for that." }, "name": { "type": "string", "maxLength": 50, "description": "Label shown in the dashboard and in alerts, up to 50 characters. Something recognisable months later beats the bare hostname." }, "isActive": { "type": "boolean", "description": "Start monitoring immediately (default true)" }, "frequency": { "type": "integer", "maximum": 1440, "minimum": 1, "description": "Check frequency in minutes (1-1440, default 5)" }, "requestTimeout": { "type": "integer", "maximum": 60, "minimum": 1, "description": "Request timeout in seconds (1-60, default 30)" } }, "additionalProperties": false }arguments 35 linescreate_ping_monitor changes data auth-required never probed
Watch a host with ICMP ping: it answers whether the machine is reachable at all, and reports round-trip time and packet loss. Use it for servers, routers and anything with no web service on top. It says nothing about whether a site or service on that host is working - a box can ping perfectly while its web server is down. Some hosting providers block ICMP, in which case the monitor will read as down.
{ "type": "object", "required": [ "name", "url" ], "properties": { "url": { "type": "string", "description": "Hostname or IP address, with no scheme and no port, for example example.com or 1.2.3.4." }, "name": { "type": "string", "maxLength": 50, "description": "Label shown in the dashboard and in alerts, up to 50 characters. Something recognisable months later beats the bare hostname." }, "isActive": { "type": "boolean", "description": "Start monitoring immediately (default true)" }, "frequency": { "type": "integer", "maximum": 1440, "minimum": 1, "description": "Check frequency in minutes (1-1440, default 5)" } }, "additionalProperties": false }arguments 29 linescreate_port_monitor changes data auth-required never probed
Watch one TCP or UDP port on a host and report it up only when the service behind it actually answers. This is the type for game servers, databases, mail and anything else that speaks its own protocol rather than HTTP - Minecraft, Rust, CS2, FiveM, Postgres, Redis, SMTP. The port must be given as part of the url. Set protocol to UDP for game servers; most of them do not answer on TCP at all.
{ "type": "object", "required": [ "name", "url" ], "properties": { "url": { "type": "string", "description": "Host and port separated by a colon, for example example.com:443 or 1.2.3.4:25565. The port is required; without it the monitor cannot be created." }, "name": { "type": "string", "maxLength": 50, "description": "Label shown in the dashboard and in alerts, up to 50 characters. Something recognisable months later beats the bare hostname." }, "isActive": { "type": "boolean", "description": "Start monitoring immediately (default true)" }, "protocol": { "enum": [ "TCP", "UDP" ], "type": "string", "description": "TCP is the default and fits most services. Use UDP for game servers and anything else that does not answer on TCP; on UDP the port counts as up only when the server actually replies." }, "frequency": { "type": "integer", "maximum": 1440, "minimum": 1, "description": "Check frequency in minutes (1-1440, default 5)" } }, "additionalProperties": false }arguments 37 linescreate_ssl_monitor changes data auth-required never probed
Watch a TLS certificate: whether it is valid, who issued it, and how many days remain before it expires. This is about the certificate, not about the site being reachable - pair it with create_http_monitor when you want both. Note that such a monitor carries two independent states, one for reachability and one for expiry, so a certificate can be days from expiring while the check still reads up.
{ "type": "object", "required": [ "name", "url" ], "properties": { "url": { "type": "string", "description": "Domain whose certificate to inspect, for example example.com. No scheme, no path." }, "name": { "type": "string", "maxLength": 50, "description": "Label shown in the dashboard and in alerts, up to 50 characters. Something recognisable months later beats the bare hostname." }, "isActive": { "type": "boolean", "description": "Start monitoring immediately (default true)" } }, "additionalProperties": false }arguments 23 linescreate_domain_monitor changes data auth-required never probed
Watch a domain registration and report how long is left before it lapses, read from WHOIS. This catches the failure no uptime check can see: everything works perfectly right up to the day the domain expires. Distinct from create_ssl_monitor, which watches the certificate rather than the registration; the two expire on different dates and both are worth watching.
{ "type": "object", "required": [ "name", "url" ], "properties": { "url": { "type": "string", "description": "Registrable domain, for example example.com. Use the registered domain rather than a subdomain: a subdomain has no registration date of its own." }, "name": { "type": "string", "maxLength": 50, "description": "Label shown in the dashboard and in alerts, up to 50 characters. Something recognisable months later beats the bare hostname." }, "isActive": { "type": "boolean", "description": "Start monitoring immediately (default true)" } }, "additionalProperties": false }arguments 23 linespause_monitor changes data auth-required never probed
Stop checking a monitor without deleting it. History and configuration survive, and resume_monitor puts it back to work. Use this around planned maintenance so the downtime does not land in the uptime figures or fire alerts. A paused monitor reports neither up nor down, so it is easy to forget one is off.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "integer", "minimum": 1, "description": "Monitor id to pause, as returned by list_monitors." } }, "additionalProperties": false }arguments 14 linesdelete_monitor changes data auth-required never probed
Permanently delete a monitor together with its entire check history, incidents and statistics. This cannot be undone and there is no trash to restore from. Confirm with the user before calling it, and prefer pause_monitor whenever the intent is only to stop the checking for a while.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "integer", "minimum": 1, "description": "Monitor id to delete, as returned by list_monitors. Deletion is irreversible." } }, "additionalProperties": false }arguments 14 linescreate_api_monitor changes data auth-required never probed
Watch a JSON or REST endpoint where the response itself matters, not only that the host answered. Use it for health endpoints, webhooks and any API whose failure would be invisible to a plain page check. For an ordinary web page, create_http_monitor is lighter and enough.
{ "type": "object", "required": [ "name", "url" ], "properties": { "url": { "type": "string", "description": "Full endpoint URL including scheme, for example https://api.example.com/v1/status." }, "name": { "type": "string", "maxLength": 50, "description": "Label shown in the dashboard and in alerts, up to 50 characters. Something recognisable months later beats the bare hostname." }, "isActive": { "type": "boolean", "description": "Start monitoring immediately (default true)" }, "frequency": { "type": "integer", "maximum": 1440, "minimum": 1, "description": "Check frequency in minutes (1-1440, default 5)" }, "requestTimeout": { "type": "integer", "maximum": 60, "minimum": 1, "description": "Request timeout in seconds (1-60, default 30)" } }, "additionalProperties": false }arguments 35 linesresume_monitor changes data auth-required never probed
Start checking a paused monitor again, with the configuration it had before. The first check runs immediately rather than after the usual interval, so the current state is known within moments. Safe to call on a monitor that is already running.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "integer", "minimum": 1, "description": "Monitor id to resume, as returned by list_monitors." } }, "additionalProperties": false }arguments 14 linesget_notifications reads auth-required 11h ago
Read the alerts this account has sent, across email, Telegram, webhook and the web interface, with the delivery outcome of each. Use it to answer "was I actually told about this outage" and to find a channel that is silently failing - a monitor can be detecting downtime correctly while its webhook has been rejecting every delivery. Covers the whole account, not one monitor.
{ "type": "object", "properties": { "page": { "type": "integer", "minimum": 1, "description": "Page number, 1-based. Defaults to 1." }, "status": { "type": "string", "description": "Return only alerts with this delivery status." }, "channel": { "enum": [ "email", "telegram", "webhook", "web" ], "type": "string", "description": "Return only alerts sent through this channel. Omit for all channels." } }, "additionalProperties": false }arguments 25 lineslist_monitors reads auth-required 11h ago
List the monitors on the account, newest first, 30 per page. Each entry carries the id needed by every other tool, plus name, url, type, current status, check frequency and the uptime percentage over the last 24 hours. Start here when the request names a monitor by name rather than by id, and when asked what is broken - filtering by status "down" answers that in one call. Returns an empty list rather than an error when nothing matches.
{ "type": "object", "properties": { "page": { "type": "integer", "minimum": 1, "description": "Page number, 1-based. Defaults to 1." }, "type": { "enum": [ "PING", "HTTP", "API", "SSL", "DOMAIN", "PORT" ], "type": "string", "description": "Return only monitors of this type. Omit for all types." }, "status": { "enum": [ "up", "down", "paused", "pending" ], "type": "string", "description": "Return only monitors in this state. \"pending\" means created but not yet checked; \"paused\" means checking is switched off, so it is neither up nor down." } }, "additionalProperties": false }arguments 33 linesget_monitor reads auth-required 30h ago
Read one monitor in full: its configuration, current status, and the type-specific detail the list view omits - expected status codes for HTTP, port and protocol for PORT, certificate or registration expiry date for SSL and DOMAIN. Use it after list_monitors when the answer depends on how the check is configured, for instance whether a timeout is too tight or which port is actually being watched.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "integer", "minimum": 1, "description": "Monitor id, as returned by list_monitors." } }, "additionalProperties": false }arguments 14 lines
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.
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, thenPOST /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-endpointwith this listing's idbd7e1142fd84ad88.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/bd7e1142fd84ad88/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/bd7e1142fd84ad88?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.