Build with it

MCP server

Add OpenPing to Claude, Cursor or any MCP client, then say what you want watched. Everything in the app is also here, so an assistant can set up and read monitoring for you.

The address

https://mcp.openping.ai

A remote server over Streamable HTTP. There is nothing to install.

Signing in

For now, the server takes an API key as the bearer token. OAuth sign-in is planned. Until then, make a key in the app under API keys and give it only the scopes you want the assistant to have: a read key can look but not change anything.

Add it

Claude Code:

claude mcp add --transport http openping https://mcp.openping.ai \
  --header "Authorization: Bearer $OPENPING_API_KEY"

Clients that read a JSON config (Cursor and others):

mcp.json

{
  "mcpServers": {
    "openping": {
      "url": "https://mcp.openping.ai",
      "headers": { "Authorization": "Bearer opk_your_key_here" }
    }
  }
}

Then say

“Watch yourapp.com and tell me in Slack if it breaks.”
“Is anything down right now?”
“Add a test that asks my agent for the refund window and checks it says 30 days.”
“Draft a status update for the open incident.”

The tools

Tool	What it does	Changes things?
`discover`	Look at a URL and suggest monitors. Creates nothing	No, read-only
`create_monitors`	Create monitors from the suggestions or from a spec, after you confirm	Yes
`list_monitors`	Every monitor with its state	No, read-only
`get_monitor`	One monitor: state, recent runs, uptime	No, read-only
`get_status`	Is everything up? Counts by state, what is not up and since when, open incidents, status pages	No, read-only
`run_check`	Run one check now and return the result	Yes, it runs a real check
`list_incidents`	Open and recent incidents	No, read-only
`get_incident`	One incident with its summary and timeline	No, read-only
`acknowledge_alert`	Say “I’m on it”, which stops the escalation	Yes
`draft_status_update`	Write a status update in plain words	No, it posts nothing
`post_status_update`	Post an update to the status page. Always needs your yes	Yes, in public
`add_agent_test`	Add a test case in plain words	Yes
`create_status_page`	Make a status page from your monitors. It stays private until a person publishes it	Yes

What keeps it safe

Read tools are marked read-only. Tools that change things carry the hints that make clients ask you first.
post_status_update never posts on an assistant’s say-so alone. It needs your yes, every time.
The server holds nothing itself. It passes your key straight to the API, which enforces the key’s scopes.

Building an agent?

See for AI agents: what each tool needs, which key scopes, and what needs a person’s yes.

We watch it with OpenPing

OpenPing’s own MCP server is watched by an MCP monitor, like any other.