ScaledPapers
REMOTE · API.SCALEDPAPERS.COM
Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.
Available components
Last scanned (20 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 2654 tokens (~78/item across 34 items; 34 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (18% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 35 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
- Tool “run_check” rewrote its description, which is the text the model reads security
- Tool “update_incident” rewrote its description, which is the text the model reads security
- 1 Nov 26 0
- Tool “update_incident” rewrote its description, which is the text the model reads security
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 30 Oct 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://api.scaledpapers.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.scaledpapers.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 6 Sept 2026 | 22 Mar 2027 | RSA 2048 | SHA256-RSA | 17b26fbc4fb2462b6e4ba3f990fd5e1 |
| SANs: api.scaledpapers.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.scaledpapers.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| scaledpapers.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.scaledpapers.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.scaledpapers.com/mcp | HTTPS enforced | 301 | https://api.scaledpapers.com:443/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
approve_incident_proposal ~92
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 text.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| impact | – | – | – |
| proposal_id | string | yes | – |
| slug | string | yes | – |
| title | – | – | – |
No output schema declared.
No examples provided.
cancel_maintenance_window ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| notify_subscribers | – | – | – |
| window_id | string | yes | – |
No output schema declared.
No examples provided.
create_check ~297
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 you want more than the default, and only within max_regions from usage. Request headers, request body, and HTTP auth stay in the console. To link a status page, pass site_id, site_slug, and component_id together.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_destination_ids | – | – | – |
| alert_email_enabled | – | – | – |
| alert_incident_enabled | – | – | – |
| body_contains | – | – | – |
| component_id | – | – | – |
| display_metrics | – | – | – |
| dns_expected_values | – | – | – |
| dns_protocol | – | – | – |
| dns_record_type | – | – | – |
| dns_server | – | – | – |
| expected_status_codes | – | – | – |
| follow_redirects | – | – | – |
| http_method | – | – | – |
| incident_auto_resolve | – | – | – |
| incident_mode | – | – | – |
| interval_seconds | – | – | – |
| kind | string | yes | – |
| name | string | yes | – |
| port | – | – | – |
| regions | – | – | – |
| site_id | – | – | – |
| site_slug | – | – | – |
| target | string | yes | – |
| tcp_expected_outcome | – | – | – |
| tcp_ip_family | – | – | – |
| tcp_payload | – | – | – |
| timeout_seconds | – | – | – |
| verify_ssl | – | – | – |
No output schema declared.
No examples provided.
create_component ~49
Add a component to an existing status page. Returns its id so update_check can link a check to it.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| slug | string | yes | – |
| url | – | – | – |
No output schema declared.
No examples provided.
create_incident ~132
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 minor, major, or critical. component_ids are component public ids. opened_at with resolved_at backfills a past incident.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| component_ids | – | – | – |
| impact | string | yes | – |
| opened_at | – | – | – |
| resolved_at | – | – | – |
| slug | string | yes | – |
| status | string | yes | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
create_maintenance_window ~141
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. Set it true only when the user asked to email subscribers. This can email subscribers, so run only when the user asked to schedule this window.
| Name | Type | Req | Description |
|---|---|---|---|
| duration_seconds | integer | yes | – |
| endpoint_ids | – | – | – |
| name | string | yes | – |
| notify_subscribers | – | – | – |
| starts_at | string | yes | – |
| status_components | – | – | – |
| timezone | string | yes | – |
| weekdays | – | – | – |
No output schema declared.
No examples provided.
create_status_page ~142
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 endpoint_ids, each check becomes a component linked to the page with incidents and latency enabled. Returns slug, publicUrl, component ids, and linked check ids. If a later step fails, the new page is deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_domain | – | – | – |
| endpoint_ids | – | – | – |
| name | string | yes | – |
| password | – | – | – |
| slug | string | yes | – |
| url | – | – | – |
| visibility | – | – | – |
No output schema declared.
No examples provided.
delete_check ~34
Delete a check. Run only when the user asked to delete this check in this conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string | yes | – |
No output schema declared.
No examples provided.
delete_component ~41
Delete a component. Run only when the user asked to delete this component in this conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
delete_status_page ~38
Delete a status page and its components. Run only when the user asked to delete this page in this conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
dismiss_incident_proposal ~37
Dismiss a pending review draft. Nothing is published.
| Name | Type | Req | Description |
|---|---|---|---|
| proposal_id | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_check ~44
One check, including assertion, DNS, and TCP fields. Secrets such as request headers, request body, and HTTP auth are not returned.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string | yes | – |
No output schema declared.
No examples provided.
get_check_results ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string | yes | – |
| hours | – | – | – |
| view | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_incident ~32
One incident, including updates newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| public_id | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_status_page ~51
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
list_alert_destinations ~36
Existing alert destinations: id, kind, name, and hint. Secrets are not returned. Creating a destination stays in the console.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_checks ~34
Checks in this workspace. Use this before create_check so you do not add a second check for a URL that is already watched.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_incident_proposals ~43
Drafts waiting for review from checks in incident_mode review, pending first. Approving one publishes it as a status incident.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
list_maintenance_windows ~39
Maintenance windows: id, name, starts_at, duration_seconds, timezone, recurrence, weekdays, ends_at, notify_subscribers, and items.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_regions ~19
Enabled probe regions: id, name, and region.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_status_pages ~34
Status pages in this workspace: slug, name, visibility, publicUrl, custom domain, and the worst open incident status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
manage_component_group ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| group_id | – | – | – |
| name | – | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
page_alert_destinations ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination_ids | array | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
post_incident_update ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| public_id | string | yes | – |
| slug | string | yes | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
run_check ~60
Queue a probe for one check from each of its live regions (the same regions a scheduled run uses). Returns job_id and regions. Call get_check_results with view status for the result; it is not included here.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint_id | string | yes | – |
No output schema declared.
No examples provided.
slack_connection ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
test_alert_destination ~38
Send a real test alert to an existing destination. Run only when the user asked to send the test.
| Name | Type | Req | Description |
|---|---|---|---|
| destination_id | string | yes | – |
No output schema declared.
No examples provided.
update_check ~270
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 approves before it is published), incident_auto_resolve, and display_metrics. Request headers, request body, and HTTP auth stay in the console.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_destination_ids | – | – | – |
| alert_email_enabled | – | – | – |
| alert_incident_enabled | – | – | – |
| body_contains | – | – | – |
| component_id | – | – | – |
| display_metrics | – | – | – |
| dns_expected_values | – | – | – |
| dns_protocol | – | – | – |
| dns_record_type | – | – | – |
| dns_server | – | – | – |
| enabled | – | – | – |
| endpoint_id | string | yes | – |
| expected_status_codes | – | – | – |
| follow_redirects | – | – | – |
| http_method | – | – | – |
| incident_auto_resolve | – | – | – |
| incident_mode | – | – | – |
| interval_seconds | – | – | – |
| name | – | – | – |
| port | – | – | – |
| regions | – | – | – |
| site_id | – | – | – |
| site_slug | – | – | – |
| target | – | – | – |
| tcp_expected_outcome | – | – | – |
| tcp_ip_family | – | – | – |
| tcp_payload | – | – | – |
| timeout_seconds | – | – | – |
| verify_ssl | – | – | – |
No output schema declared.
No examples provided.
update_component ~41
Rename a component or change its URL.
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | string | yes | – |
| name | – | – | – |
| slug | string | yes | – |
| url | – | – | – |
No output schema declared.
No examples provided.
update_incident ~113
Edit an incident's title or impact. Run only when the user asked. With update_id and update_body, rewrite that posted update's message (no new notification). To change status, post a message, or resolve, use post_incident_update instead.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| component_ids | – | – | – |
| impact | – | – | – |
| public_id | string | yes | – |
| slug | string | yes | – |
| status | – | – | – |
| title | – | – | – |
| update_body | – | – | – |
| update_id | – | – | – |
No output schema declared.
No examples provided.
update_maintenance_window ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| duration_seconds | – | – | – |
| endpoint_ids | – | – | – |
| name | – | – | – |
| notify_subscribers | – | – | – |
| starts_at | – | – | – |
| status_components | – | – | – |
| timezone | – | – | – |
| weekdays | – | – | – |
| window_id | string | yes | – |
No output schema declared.
No examples provided.
update_status_page ~113
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 least 8 characters that the user typed. Never invent a password or repeat it.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_domain | – | – | – |
| name | – | – | – |
| password | – | – | – |
| show_auto_detected | – | – | – |
| slug | string | yes | – |
| url | – | – | – |
| visibility | – | – | – |
No output schema declared.
No examples provided.
usage ~61
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 reached.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_custom_domain ~30
Check the CNAME and TXT records for a status page custom domain.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
How do I install the ScaledPapers MCP server?
ScaledPapers is a hosted endpoint at https://api.scaledpapers.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.scaledpapers.com
claude mcp add --transport http com-scaledpapers-scaledpapers 'https://api.scaledpapers.com/mcp'
What is the ScaledPapers MCP server?
ScaledPapers is an MCP server listed in the public MCP registry as com.scaledpapers/scaledpapers. Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP. This page covers its hosted endpoint (https://api.scaledpapers.com/mcp).
Is the ScaledPapers MCP server safe to use?
ScaledPapers scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ScaledPapers MCP server expose?
ScaledPapers exposes 34 tools: usage, list_regions, list_checks, get_check, get_check_results, and 29 more. Their descriptions and schemas cost roughly 2,562 tokens of context every time the server is loaded.
Does the ScaledPapers MCP server require authentication?
Yes. ScaledPapers asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the ScaledPapers MCP server still maintained?
ScaledPapers is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.