Uptime monitoring and status pages

Monitor so that you know it first. Your customers hear it from you.

ScaledPapers confirms a failure, opens the incident, and updates the status page before anyone has to write in, replacing a Pingdom and Statuspage stack.

Start free monitoring See it live Talk to Nurbol

Free for 5 checks. Pro is $15/mo flat. No card for Free.

Multi-region checks
Status pages
MCP + REST API

Onboard your agent: Agent setup prompt

All systems live Checks run every 60 s on Pro · 5 min on Free

Uptime 99.98% · 90 days Check types HTTP · API · DNS · TCP Alerts Email · Slack · Webhooks

01MCP server

Your agent can set this up.

Install the agent skill, export one API key, run bash ~/.agents/skills/scaledpapers/scripts/wire-mcp.sh, and Claude Code, Cursor, or Codex can create checks, build the status page, open incidents, and schedule maintenance over MCP. 31 tools, no OAuth dance. Read the MCP docs.

on-call@laptop — claude

Exposed tools31 total

usageplan caps and what is used
create_checkHTTP, API, DNS, or TCP check
run_checkprobe once, right now
create_status_pagepage plus linked components
create_incidentopen an incident from an agent
create_maintenance_windowschedule and announce
list_checksevery check in the workspace
get_checkone check, no secrets
get_check_resultsrecent probes per region
update_checkinterval, regions, pause, link
delete_checkremove a check
list_regionsprobe locations
list_status_pagespages in the workspace
get_status_pagecomponents, domain, Slack
update_status_pagename, visibility, domain
delete_status_pageremove a page
verify_custom_domaincheck the CNAME
create_componentadd a component
update_componentrename or relink
delete_componentremove a component
manage_component_groupgroup components
slack_connectionstart or disconnect Slack
page_alert_destinationsattach existing destinations
get_incidenttimeline and updates
update_incidentstatus, impact, resolve
post_incident_updatetell subscribers
list_maintenance_windowsupcoming and past
update_maintenance_windowreschedule
cancel_maintenance_windowcall it off
list_alert_destinationsSlack, PagerDuty, webhooks
test_alert_destinationsend a test alert

Team, API keys, billing, and destination secrets stay in the console. Full list.

02Alerts

One failed check is noise. Two in a row is an incident.

A single failure is recorded, nothing more. When the confirmation period you set is met, the check goes down, an incident opens on the linked component, and one alert goes out. Recovery resolves it on its own.

Confirmation period is yours to set: 1, 2, 3, or 5 checks. Recovery: 1, 2, or 3.

Alerted

prod.api

Resolved

Checking every interval
1 failed check · recorded, not sent
2 in a row · incident opened, alert sent
Checks passing · incident resolved

03Dashboard

The dashboard

Every check in the workspace on one screen: status, response time per region, incidents, and the last probe. API, website, DNS, and TCP checks side by side.

workspace · all checks Last check · just now

5/5 operational http · api · dns · tcp

04Regions

Monitor from anywhere

Point a check at any URL, host, or port. Probes run across North America, Europe, Asia Pacific, and South America.

San Francisco · us-west-1 Portland · us-west-2 Ashburn · us-east-1 Columbus · us-east-2 Montreal · ca-central-1 Frankfurt · eu-central-1 São Paulo · sa-east-1 Singapore · ap-southeast-1 Sydney · ap-southeast-2

San Franciscous-west-1
132 ms
Portlandus-west-2
128 ms
Ashburnus-east-1
88 ms
Columbusus-east-2
96 ms
Montrealca-central-1
98 ms
Frankfurteu-central-1
112 ms
São Paulosa-east-1
164 ms
Singaporeap-southeast-1
186 ms
Sydneyap-southeast-2
204 ms

05Status pages

Your own domain, your status page

status.yourcompany.com instead of a vendor URL. Add the subdomain, point the CNAME, and the page is served there over HTTPS. The checks you already run feed the components, uptime bars, and response-time charts.

One CNAME and a TXT challengeCopy the two records, add them at your DNS provider, click Verify DNS.
HTTPS handledThe certificate is issued and renewed for you once DNS verifies.
Drift detectionIf the record changes, the console flags it and the page recovers when it is back.
Private pagesPassword-protected pages for internal services, on the same domain.

Custom domainPage settings

status.acme.com Needs DNS record

CNAME status.acme.com → cname.scaledpapers.com TTL 300

Add your subdomain
Point the CNAME
Live over HTTPS

06Incident lifecycle

From incident detected to resolved and customers updated

Most monitors page you and leave. Here the check runs the incident: opens it, posts to the status page, notifies subscribers, resolves it, and keeps the record.

00:00 UTC

Check fails

07Wire it in

Built for engineers. Add monitoring on the go.

Click in the console, ask your agent over MCP, or call the REST API. Same checks, same status pages, same incidents under all three. API requests are unlimited and never billed.

# One key from /app/api-keys, exported in your shell
export SP_API_KEY=sp_…

claude mcp add --transport http scaledpapers https://api.scaledpapers.com/mcp \
  --header "Authorization: Bearer ${SP_API_KEY}"

# Then just ask:
#   "Is anything down right now?"
#   "Watch the health URLs in this repo and put them on a status page"

Codex users: add [mcp_servers.scaledpapers] to ~/.codex/config.toml. See MCP docs.

// ~/.cursor/mcp.json or .cursor/mcp.json
{
  "mcpServers": {
    "scaledpapers": {
      "url": "https://api.scaledpapers.com/mcp",
      "headers": { "Authorization": "Bearer ${env:SP_API_KEY}" }
    }
  }
}

Cursor allows 40 MCP tools across all servers; this one uses 31. The key is read from your environment, never from the file.

curl -X POST https://api.scaledpapers.com/v1/endpoints \
  -H "Authorization: Bearer sp_…" \
  -H "Content-Type: application/json" \
  -d '{
    "target": "https://api.example.com/health",
    "interval_seconds": 60,
    "regions": ["us-west-1", "us-east-1"]
  }'

{
  "id": "8f2a…",
  "name": "api.example.com/health",
  "target": "https://api.example.com/health",
  "enabled": true,
  "interval_seconds": 60,
  "regions": ["us-west-1", "us-east-1"]
}

Full reference in the API docs and the public Status API.

08Pricing

Flat $15. Custom domain included.

No per-seat, no per-alert, no trial that charges your card. Free is free forever. Pro is one price for the whole workspace.

Free forever

Free

$0 no card

For side projects and trying the console.

5 checks (API, website, DNS, or TCP)
5-minute interval · 1 region of your choice
14 days of check results
1 public status page with Slack subscribe
Email alerts
Full REST API and MCP server

Start free

For production

Pro

$15 per month

One price for the workspace. Everyone on the team is included.

Custom domain for your status page (status.yourcompany.com)
Private status pages
Slack, Discord, PagerDuty, Pushover, and webhook alerts
25 checks · 60-second interval · 5 regions
90 days of check results
5 status pages
Everything in Free

Start free, upgrade in Settings

For larger fleets

Enterprise

Custom

For teams that need more than Pro.

Everything in Pro, plus:

Custom check volume
Custom terms

Talk to Nurbol

What happens if I go over Free?: The console and API refuse a sixth check, a faster interval, or a second region. Nothing is charged. Pro raises the caps.
How does billing work?: Pro is billed monthly or yearly by our payment provider as merchant of record. Subscribe from Settings for the workspace you pick. Refund policy.
Is the API metered?: No. API and MCP requests are unlimited on both plans. You pay only for more checks, faster intervals, more regions, and longer history. Full pricing FAQ.
How do you monitor the monitoring service itself?: Our website, API, and status page are checks in ScaledPapers. The page is public. CloudWatch pages us if the probes stop.

09Demo

See the whole thing in three minutes

A website check goes live, then a status page gets its first incident and update.

You build it. We monitor it.

Start free monitoring Talk to Nurbol

Free for 5 checks, no card. Pro is $15/mo when a side project becomes production.