Talk to your monitoring

What this is

MCP (Model Context Protocol) is the standard AI assistants use to reach outside tools. YoPingMe runs an MCP server at https://app.yoping.me/api/mcp with six tools, so an assistant like Claude can read your monitors and answer questions about them. Five of the six only read. It comes with every plan, the free one included.

What you can ask

The five read-only tools, in the order you will probably meet them:

• list_monitors: every monitor with its current status per region.
• get_uptime_report: a monitor's uptime, day by day.
• list_incidents: outages with durations and total downtime.
• get_performance_metrics: response times for a monitor.
• get_failing_checks: the actual errors a failing check got back.

And one that writes: create_monitor starts watching a new URL, so you can add a site by asking rather than by opening the dashboard. It is the only tool that changes anything, it makes HTTP monitors only, and it is refused unless the key you gave the assistant carries the mcp:write scope.

Which means questions like these get real answers: "did checkout go down this week?", "how long was Tuesday's outage?", "what exactly is my API monitor seeing right now?"

How to connect Claude, Cursor, or another MCP client

In the dashboard, open the Account page and create an MCP API key. The key is shown once, so copy it then. In Claude Code, adding the server is one command:

claude mcp add --transport http yopingme https://app.yoping.me/api/mcp --header "Authorization: Bearer YOUR_KEY"

Or in a project's .mcp.json:

{
  "mcpServers": {
    "yopingme": {
      "type": "http",
      "url": "https://app.yoping.me/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

Those same two values - the URL and the header - are all any other client needs. Cursor, VS Code, Codex CLI, Cline, Zed and Claude Desktop each take a remote MCP server with a custom header, so the setup is the same shape wherever you work. Anything that speaks streamable HTTP and can send an Authorization header will do.

What the free plan includes

Answers cover the last 7 days, with a 24-hour window for raw failing-check detail. You get 50 questions a day, and reports are per monitor. Those are the edges of the free plan, stated plainly; inside them, everything above works. The paid Pro and Team plans widen those edges - unlimited uptime history, account-wide reports, and 1,000 or 5,000 questions a day. You can upgrade from your account page; both start with a 14-day free trial.

What a key can and cannot do

An MCP key reaches the MCP server and nothing else. Write access is a separate, opt-in scope: unless you tick it when you create the key, all six tools behave as read-only and an assistant holding that key can look at monitoring data without changing anything. Tick it and one tool unlocks, create_monitor. Even then nothing can be edited, paused or deleted, and alerts stay out of reach entirely. A key is never a general API credential, the product's REST API refuses it, and you can revoke any key on the same Account page, any time.

The whole thing takes a few minutes: sign up at app.yoping.me, add a monitor, create a key, and the next "is my site up?" can go to Claude instead of a browser tab.