mcpbeat Sign in

Notifario MCP Server

answering

Notifario is answering right now. Last checked moments ago.

Website and server uptime monitoring from Russia and Europe: monitors, incidents, SSL, DNS.

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
266 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Notifario every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add notifario --transport http https://notifar.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://notifar.io/mcp
~/.codex/config.toml
[mcp_servers.notifario]
url = "https://notifar.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "notifario": {
      "url": "https://notifar.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "notifario": {
      "type": "http",
      "url": "https://notifar.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://notifar.io/mcp streamable-http sign-in 261 ms 0 min ago

Alternatives to Notifario

same job, measured the same way
Monitoring
by pingvera

Client-website monitoring for agencies: uptime, incidents, SSL/domain expiry, server metrics.

answering
HostTracker
by hosttracker

Website uptime monitoring: run checks from 300+ locations, manage monitors, alerts and incidents

65 tools answering
UptimeRobot
by uptimerobot

Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.

answering
Xitoring
by xitoring

Connect AI assistants to Xitoring monitoring: servers, uptime, incidents, metrics, SSL, and alerts.

answering
StatOSS
by statoss

Status pages and uptime monitoring: read status, monitors and incidents; open incidents.

answering
Openuptime
by openuptime

Manage uptime monitors, incidents and status pages from any MCP client.

answering
All's Well
by alls-well

Set up uptime, SSL and heartbeat monitors, alert contacts and incidents for an All's Well team.

answering
Site Qwality
by siteqwality

Manage uptime monitors and incidents and search logs, metrics and traces from an AI assistant.

answering

Notifario — questions

Answers built from our own checks of this server.

Why is there no tool list for Notifario?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Notifario working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 266 ms. The bar chart above shows every period we have measured.
How do I connect Notifario?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Notifario?
No API key is involved. Notifario answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Notifario?
It answers our handshake in 266 ms on average, which is faster than 54% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.