Home / MCP registry index / io.usefulapi/updown-io
updown.io MCP by usefulapi
io.usefulapi/updown-io in the official MCP registry.
Endpoint https://updown-io.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Check updown.io uptime checks, downtimes, response metrics and status pages, and create checks.
We read its 14 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
updown_list_checks updown_get_check updown_list_downtimes updown_get_check_metrics updown_find_problems updown_list_recipients updown_list_status_pages updown_list_nodes updown_list_node_ips updown_create_check updown_update_check updown_add_recipient updown_create_status_page updown_update_status_page
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-updown-io)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.