ScaledPapers

MCP server · hosted · v1.0.0 · com.scaledpapers/scaledpapers

Online · tested 1h agoNEW · 2h agoSeen in the registry 1h ago

Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.

What it does

ScaledPapers is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES

Local installNO

Live checkOnline · 34 tools

Version1.0.0

PriceNot in the registry

First seen30 Oct 2026

Last checked1h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1h ago (live check)

Hosted endpoint

https://api.scaledpapers.com/mcp streamable-http

Required: Authorization (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "scaledpapers": {
      "url": "https://api.scaledpapers.com/mcp",
      "headers": {
        "Authorization": "<your Authorization>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 1h ago

ONLINE ScaledPapers answered an MCP connection on 30 Oct 2026 and introduced itself as ScaledPapers (MCP protocol 2025-06-18).

34 tools offered to AI assistants

usage · Plan caps for this workspace: plan, period, probe_count, monthly_probe_quota, endpoints_used, max_endpoints, max_regions, min_interval_seconds, sample_retention_days, max_status_pages. Call this before creating anything. Stop when a cap is
list_regions · Enabled probe regions: id, name, and region.
list_checks · Checks in this workspace. Use this before create_check so you do not add a second check for a URL that is already watched.
get_check · One check, including assertion, DNS, and TCP fields. Secrets such as request headers, request body, and HTTP auth are not returned.
get_check_results · Check results. view is status, history, or outages. history uses hours (default 24) and returns status, status_code, latency_ms, dns_ms, connect_ms, location_name, location_region, and observed_at. Sample metadata is omitted.
create_check · Create a check. kind is http, api, dns, or tcp. Defaults: GET, status 200, 10s timeout, email alerts on, interval_seconds from the plan minimum, and one region. DNS defaults to an A record over UDP. TCP requires port. Pass regions only when
update_check · Update a check. Pass only the fields to change. enabled false pauses and true resumes. Linking requires site_id, site_slug, and component_id together, plus optional incident_mode (off, auto, or review: review stores a draft a person approve
delete_check · Delete a check. Run only when the user asked to delete this check in this conversation.
run_check · Queue a probe for one check. Returns job_id. Call get_check_results with view status for the result; it is not included here.
list_status_pages · Status pages in this workspace: slug, name, visibility, publicUrl, custom domain, and the worst open incident status.
get_status_page · One status page: components with ids, groups, incidents with public ids, Slack connection state, and alert-destination ids. has_password is returned; the password is not.
create_status_page · Create a public status page. visibility internal requires Pro and a password of at least 8 characters that the user typed; never invent a password or repeat it. custom_domain is a hostname such as status.acme.com and requires Pro. With endp

Show 22 more

update_status_page · Update a status page. Fields: name, url, visibility, password, custom_domain, show_auto_detected (label incidents a check opened itself as detected automatically). custom_domain null removes it. visibility internal needs a password of at le
delete_status_page · Delete a status page and its components. Run only when the user asked to delete this page in this conversation.
verify_custom_domain · Check the CNAME and TXT records for a status page custom domain.
create_component · Add a component to an existing status page. Returns its id so update_check can link a check to it.
update_component · Rename a component or change its URL.
delete_component · Delete a component. Run only when the user asked to delete this component in this conversation.
manage_component_group · Create, update, or delete a component group. action is create, update, or delete. create and update need name. update and delete need group_id. Delete only when the user asked.
slack_connection · Slack connection for a status page. action start returns a URL for the user to open; do not complete OAuth. action disconnect removes the connection. Disconnect only when the user asked. Connection state is on get_status_page.
page_alert_destinations · Replace the alert destinations attached to a status page with these existing destination ids. Use list_alert_destinations for the ids. An empty list detaches all of them.
list_incident_proposals · Drafts waiting for review from checks in incident_mode review, pending first. Approving one publishes it as a status incident.
approve_incident_proposal · Publish a pending review draft as a status incident. This emails subscribers and posts to Slack. Run only when the user asked to publish it in this conversation. Optional title, body, and impact (minor, major, or critical) replace the draft
dismiss_incident_proposal · Dismiss a pending review draft. Nothing is published.
create_incident · Open an incident. This emails subscribers and posts to Slack the same way the console does. Run only when the user asked to publish this incident in this conversation. status is investigating, identified, monitoring, or resolved. impact is
get_incident · One incident, including updates newest first.
update_incident · Edit an incident. This can email subscribers and post to Slack. Run only when the user asked. With update_id, edit that posted update instead of the incident. Never invent a status the user did not ask for.
post_incident_update · Post an incident update. This emails subscribers and posts to Slack. Run only when the user asked to publish this update in this conversation. status resolved closes the incident.
list_maintenance_windows · Maintenance windows: id, name, starts_at, duration_seconds, timezone, recurrence, weekdays, ends_at, notify_subscribers, and items.
create_maintenance_window · Schedule a maintenance window. duration_seconds is 60 through 7 days. Pass both the check (endpoint_ids) and its public component (status_components) so probes pause and the page shows Under maintenance. notify_subscribers defaults to false
update_maintenance_window · Update a maintenance window. notify_subscribers defaults to false unless you set it. This can email subscribers. Run only when the user asked to change this window.
cancel_maintenance_window · Cancel a maintenance window. notify_subscribers defaults to false. This can email subscribers. Run only when the user asked to cancel this window in this conversation.
list_alert_destinations · Existing alert destinations: id, kind, name, and hint. Secrets are not returned. Creating a destination stays in the console.
test_alert_destination · Send a real test alert to an existing destination. Run only when the user asked to send the test.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.

Fact	Value	Evidence	Source	Last confirmed
Hosted endpoint	https://api.scaledpapers.com/mcp	DECLARED	SRC-001 Official MCP Registry	1h ago
Local install (package)	no	DECLARED	SRC-001 Official MCP Registry	1h ago
Remote access (hosted)	yes	DECLARED	SRC-001 Official MCP Registry	1h ago
Website	https://scaledpapers.com/docs/mcp/	DECLARED	SRC-001 Official MCP Registry	1h ago
Registry status	active	DECLARED	SRC-001 Official MCP Registry	1h ago
Version	1.0.0	DECLARED	SRC-001 Official MCP Registry	1h ago
MCP server	yes	DECLARED	SRC-001 Official MCP Registry	1h ago

Change history

NEW30 Oct 2026
first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Is ScaledPapers still online?

Free alerts · no account

Do you run ScaledPapers? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor ScaledPapersLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Questions about ScaledPapers

How do I connect ScaledPapers?

Use the hosted endpoint https://api.scaledpapers.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does ScaledPapers need an API key or token?

Yes. The registry entry lists a required value: Authorization. Get it from the publisher.

What tools does ScaledPapers offer?

When Electra Index connected on 30 Oct 2026, it listed 34 tools: usage, list_regions, list_checks, get_check, get_check_results, create_check, update_check, delete_check and more. The full list is in "Live check" above.

Is ScaledPapers online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1h ago.