io.usefulapi/checkly
REMOTE · CHECKLY.USEFULAPI.IO · SCANNED SEP 20
Query Checkly synthetic monitoring — checks, statuses, results, alerts, reporting and dashboards.
Available components
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1643 tokens (~74/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/checkly MCP server?
io.usefulapi/checkly is a hosted endpoint at https://checkly.usefulapi.io/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 · checkly.usefulapi.io
claude mcp add --transport http io-usefulapi-checkly 'https://checkly.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-checkly": {
"url": "https://checkly.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-checkly": {
"type": "http",
"url": "https://checkly.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-checkly] url = "https://checkly.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-checkly": {
"type": "remote",
"url": "https://checkly.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-checkly --url 'https://checkly.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-checkly:
url: "https://checkly.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-checkly": {
"Transport": "http",
"Url": "https://checkly.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-checkly -t streamable-http -u 'https://checkly.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-checkly": {
"type": "http",
"url": "https://checkly.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 8 Sept 26 0
- Stability: 0.97 → pass security
- 7 Sept 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 0
- Authorization: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Stability: unverified → 0.43 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 8 Aug 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 2026 · Probed https://checkly.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f857fedf684a4ec413c17ff93051aaa9 |
| SANs: usefulapi.io, checkly.usefulapi.io, *.checkly.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of checkly.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://checkly.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://checkly.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://checkly.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://checkly.usefulapi.io/mcp |
| Authorisation server | https://checkly.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://checkly.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://checkly.usefulapi.io/mcp | Inconclusive | 401 |
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 →
checkly_create_maintenance_window Create maintenance window ~192
MODIFIES THE CHECKLY ACCOUNT: schedules a maintenance window that silences alerts for a time range (e.g. during a deploy). Omit repeatUnit for a one-off window. Public API: POST /v1/maintenance-windows.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional description. |
| endsAt | string | yes | End time, ISO-8601. |
| name | string | yes | Maintenance window name. |
| repeatUnit | string | – | For a recurring window: DAY, WEEK, or MONTH. Omit for one-off. |
| silenceAllAlerts | boolean | – | Silence alerts for ALL checks (overrides tag scoping). |
| startsAt | string | yes | Start time, ISO-8601 (e.g. 2026-07-15T22:00:00.000Z). |
| tags | array | – | Tags of checks/groups to include in the window. |
No output schema declared.
No examples provided.
checkly_create_variable Create environment variable ~103
MODIFIES THE CHECKLY ACCOUNT: creates a new account-level environment variable. Additive (does not overwrite existing keys). Public API: POST /v1/variables.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The variable key (cannot be changed later). |
| locked | boolean | – | Hide the value like a password in the UI. |
| secret | boolean | – | Mark as secret — value becomes write-only after creation. |
| value | string | yes | The variable value. |
No output schema declared.
No examples provided.
checkly_get_account Get current account ~32
Fetch details of the Checkly account tied to your credentials. Public API: GET /v1/accounts/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
checkly_get_check Get a check ~59
Retrieve a single check's full configuration by id. Public API: GET /v1/checks/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The check id. |
| includeDependencies | boolean | – | Include dependent resources (snippets, alert channels). |
No output schema declared.
No examples provided.
checkly_get_check_alerts Get alerts for a check ~98
List alert notifications for one specific check. Public API: GET /v1/check-alerts/{checkId}.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | The check id. |
| from | integer | – | Start of range as a Unix timestamp (seconds). |
| limit | integer | – | Page size. |
| page | integer | – | 1-based page number. |
| to | integer | – | End of range as a Unix timestamp (seconds). |
No output schema declared.
No examples provided.
checkly_get_check_group Get a check group ~43
Retrieve a single check group by id. Public API: GET /v1/check-groups/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The check group id. |
No output schema declared.
No examples provided.
checkly_get_check_result Get a check result ~61
Retrieve a single check-run result in full. Public API: GET /v1/check-results/{checkId}/{checkResultId}.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | The check id. |
| checkResultId | string | yes | The check result id. |
No output schema declared.
No examples provided.
checkly_get_check_status Get check status ~46
Retrieve the current status details for a single check. Public API: GET /v1/check-statuses/{checkId}.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | The check id. |
No output schema declared.
No examples provided.
checkly_get_reporting Get reporting ~148
Aggregated availability / performance / SLA report across checks and groups. Public API: GET /v1/reporting.
| Name | Type | Req | Description |
|---|---|---|---|
| filterByTags | string | – | Filter by a tag. |
| from | integer | – | Start of range as a Unix timestamp (seconds). |
| granularity | string | – | Bucket size for time series. |
| quickRange | string | – | Preset range, e.g. last24Hrs, last7Days, last30Days, thisWeek, thisMonth, lastWeek, lastMonth. |
| timezone | string | – | IANA timezone, e.g. Europe/Berlin. |
| to | integer | – | End of range as a Unix timestamp (seconds). |
No output schema declared.
No examples provided.
checkly_list_alert_channels List alert channels ~65
List all alert channels (email, Slack, webhook, PagerDuty, etc.) configured in the account. Public API: GET /v1/alert-channels.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Page size. |
| page | integer | – | 1-based page number. |
No output schema declared.
No examples provided.
checkly_list_check_alerts List check alerts ~86
List recent alert notifications fired across the whole account. Public API: GET /v1/check-alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| from | integer | – | Start of range as a Unix timestamp (seconds). |
| limit | integer | – | Page size. |
| page | integer | – | 1-based page number. |
| to | integer | – | End of range as a Unix timestamp (seconds). |
No output schema declared.
No examples provided.
checkly_list_check_groups List check groups ~78
List all check groups (shared config for a set of checks). Public API: GET /v1/check-groups.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Page size. |
| name | string | – | Filter by group name. |
| page | integer | – | 1-based page number. |
| tag | string | – | Filter by a tag. |
No output schema declared.
No examples provided.
checkly_list_check_results List check results ~154
List individual run results for a check (latency, success, location, response). Public API: GET /v1/check-results/{checkId}.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | The check id. |
| from | integer | – | Start of range as a Unix timestamp (seconds). |
| hasFailures | boolean | – | Only return results that contain failures. |
| limit | integer | – | Page size. |
| location | string | – | Filter by run location, e.g. eu-west-1. |
| page | integer | – | 1-based page number. |
| resultType | string | – | FINAL, ATTEMPT, or ALL. |
| to | integer | – | End of range as a Unix timestamp (seconds). |
No output schema declared.
No examples provided.
checkly_list_check_statuses List check statuses ~46
List the current pass/fail/degraded status of every check — the 'what's down right now' view. Public API: GET /v1/check-statuses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
checkly_list_checks List checks ~111
List all synthetic monitoring checks (API, browser, URL, heartbeat, etc.) in the account. Public API: GET /v1/checks.
| Name | Type | Req | Description |
|---|---|---|---|
| checkType | string | – | Filter by check type, e.g. API, BROWSER, URL, HEARTBEAT. |
| limit | integer | – | Page size. |
| page | integer | – | 1-based page number. |
| search | string | – | Free-text search across check names. |
| tag | string | – | Filter by a tag. |
No output schema declared.
No examples provided.
checkly_list_dashboards List dashboards ~50
List all public/private status dashboards. Public API: GET /v1/dashboards.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Page size. |
| page | integer | – | 1-based page number. |
No output schema declared.
No examples provided.
checkly_list_locations List locations ~32
List all public checking locations Checkly can run checks from. Public API: GET /v1/locations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
checkly_list_maintenance_windows List maintenance windows ~58
List all maintenance windows (periods where alerts are silenced). Public API: GET /v1/maintenance-windows.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Page size. |
| page | integer | – | 1-based page number. |
No output schema declared.
No examples provided.
checkly_list_private_locations List private locations ~33
List all private (self-hosted) checking locations. Public API: GET /v1/private-locations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
checkly_list_runtimes List runtimes ~40
List all supported runtimes (Node versions + bundled dependencies) for browser/API checks. Public API: GET /v1/runtimes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
checkly_list_snippets List snippets ~48
List all reusable code snippets. Public API: GET /v1/snippets.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Page size. |
| page | integer | – | 1-based page number. |
No output schema declared.
No examples provided.
checkly_list_variables List variables ~60
List all account-level environment variables. Note: secret variable values are redacted by the API. Public API: GET /v1/variables.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Page size. |
| page | integer | – | 1-based page number. |
No output schema declared.
No examples provided.
What is the io.usefulapi/checkly MCP server?
io.usefulapi/checkly is an MCP server listed in the public MCP registry as io.usefulapi/checkly. Query Checkly synthetic monitoring, checks, statuses, results, alerts, reporting and dashboards. This page covers its hosted endpoint (https://checkly.usefulapi.io/mcp).
Is the io.usefulapi/checkly MCP server safe to use?
io.usefulapi/checkly scores 85 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 io.usefulapi/checkly MCP server expose?
io.usefulapi/checkly exposes 22 tools: checkly_get_account, checkly_list_checks, checkly_get_check, checkly_list_check_groups, checkly_get_check_group, and 17 more. Their descriptions and schemas cost roughly 1,643 tokens of context every time the server is loaded.
Does the io.usefulapi/checkly MCP server require authentication?
Yes. io.usefulapi/checkly 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 io.usefulapi/checkly MCP server still maintained?
io.usefulapi/checkly is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.