Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Checkly (BYOK) icon

Checkly (BYOK)

Read your Checkly monitoring checks, current pass/fail status, recent results, alerts, check groups and maintenance windows with BYOK and account id

Unify Dynamics LLC

Tools9read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderChecklyunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which Checkly account and plan am I on?
Tools called
get_account
Which of my Checkly checks are failing?
Tools called
list_checks
Show details of my Checkly check
Tools called
get_check
What is the current status of all my Checkly checks?
Tools called
list_check_statuses
Is my Checkly check passing right now?
Tools called
get_check_status
How did my Checkly check run in the last hours?
Tools called
list_check_results

About

Checkly (BYOK) lets an AI assistant read your own Checkly data through the Checkly API with a key you supply (Checkly user API key). Read-only: 9 tools (get_account, list_checks, get_check, list_check_statuses, get_check_status, list_check_results, list_check_alerts, list_check_groups, list_maintenance_windows). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.checklyhq.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Checkly. Checkly and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Checkly API (api.checklyhq.com) with a BYOK key; documentation: https://www.checklyhq.com/docs/api-reference/overview. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data9 tools
  • Get accountShow the current Checkly account: id, name and plan.
  • List checksList monitoring checks (API, browser, heartbeat, URL, TCP, DNS, SSL and more) with type, frequency in minutes, locations, tags and mute state.
  • Get checkGet one check by id: type, frequency, locations, tags, thresholds and request URL and method (no scripts or headers).
  • List check statusesList the current status of all checks: failing, errored or degraded flags, fastest and slowest recent run in ms, last run location and days until…
  • Get check statusGet the current status of one check: failure, error and degraded flags, run times and SSL days remaining.
  • List check resultsList recent runs of a check with pass/fail flags, location, start time and response time in ms.
  • List check alertsList alerts raised across all checks (failure, recovery, degraded, SSL) with check, location, error and time.
  • List check groupsList check groups with name, activation, mute state, tags and locations.
  • List maintenance windowsList maintenance windows with name, start and end, repeat interval, time zone and tags.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-checkly.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 9 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-checkly.connectorbay.com/mcp
RESTPOST https://byok-checkly.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-checkly.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Checkly user API key in the X-Upstream-Key header (get one at app.checklyhq.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Checkly connector: questions and answers

What is the Checkly connector?

Checkly (BYOK) lets an AI assistant read your own Checkly data through the Checkly API with a key you supply (Checkly user API key). It is a hosted MCP server with 9 tools such as Get account, List checks, Get check, List check statuses, Get check status, List check results, published by Unify Dynamics LLC. It is independent and not affiliated with Checkly.

How do I connect Checkly to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-checkly.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-checkly.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-checkly.json.

Do I need a Checkly account or API key?

Yes: this is a bring-your-own-key connector. Create a Checkly user API key at https://app.checklyhq.com/settings/user/api-keys and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Checkly read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Checkly connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

mabl (BYOK)

Read your mabl test automation workspace: applications, environments, test and plan runs, deployment events, issues and Link Agents, with your own API key

Live · MCP + REST10 tools

Mackerel (BYOK)

Read your Mackerel server monitoring: hosts, services, roles, metrics, monitors and alerts (Japan) with your own read-only API key

Live · MCP + REST12 tools

Mailfornet (BYOK)

Read the disposable inbox message lists, sending domains, webhook endpoints and monthly request usage of your Mailfornet test-email account with your own API key; it never creates or deletes inboxes

Live · MCP + REST5 tools

Mailgun (BYOK)

Read your Mailgun sending domains, delivery events, stats, bounces, complaints and unsubscribes with BYOK (US region, read-only)

Live · MCP + REST10 tools

Mailosaur (BYOK)

Read your Mailosaur email and SMS testing inboxes, message summaries, deliverability reports and usage limits with your own API key

Live · MCP + REST6 tools

Manifest Cyber (BYOK)

Read your Manifest Cyber SBOM inventory: assets, components, SBOM records, suppliers and vulnerability risk, with your own API token

Live · MCP + REST12 tools

Documentation

Back to top

Checkly (BYOK) — connector documentation

  • MCP endpoint: https://byok-checkly.connectorbay.com/mcp
  • REST API: POST https://byok-checkly.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-checkly.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Checkly Checkly user API key, sent in the X-Upstream-Key header and the Checkly account id in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-checkly.connectorbay.com/health · Tool schemas: https://byok-checkly.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-checkly · agent@connectorbay.com

What Checkly (BYOK) is for

Checkly (BYOK) lets an AI assistant read your own Checkly data through the Checkly API with a key you supply (Checkly user API key). Read-only: 9 tools (get_account, list_checks, get_check, list_check_statuses, get_check_status, list_check_results, list_check_alerts, list_check_groups, list_maintenance_windows). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.checklyhq.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Checkly. Checkly and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Checkly account and plan am I on?"
  • "Which of my Checkly checks are failing?"
  • "Show details of my Checkly check"
  • "What is the current status of all my Checkly checks?"
  • "Is my Checkly check passing right now?"
  • "How did my Checkly check run in the last hours?"

What it does

  • get_account: Show the current Checkly account: id, name and plan.
  • list_checks: List monitoring checks (API, browser, heartbeat, URL, TCP, DNS, SSL and more) with type, frequency in minutes, locations, tags and mute state. Filter by type, current status, tag or name text.
  • get_check: Get one check by id: type, frequency, locations, tags, thresholds and request URL and method (no scripts or headers).
  • list_check_statuses: List the current status of all checks: failing, errored or degraded flags, fastest and slowest recent run in ms, last run location and days until the SSL certificate expires.
  • get_check_status: Get the current status of one check: failure, error and degraded flags, run times and SSL days remaining.
  • list_check_results: List recent runs of a check with pass/fail flags, location, start time and response time in ms. Default window is the last 6 hours; use from and to Unix timestamps for another.
  • list_check_alerts: List alerts raised across all checks (failure, recovery, degraded, SSL) with check, location, error and time. Default window is the last 6 hours.
  • list_check_groups: List check groups with name, activation, mute state, tags and locations.
  • list_maintenance_windows: List maintenance windows with name, start and end, repeat interval, time zone and tags.

BYOK key

You bring your own Checkly Checkly user API key (https://app.checklyhq.com/settings/user/api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.checklyhq.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Checkly API (api.checklyhq.com) with a BYOK key; documentation: https://www.checklyhq.com/docs/api-reference/overview. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Checkly. Checkly and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Checkly account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Checkly (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Checkly (BYOK) is. Checkly (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Checkly data: Read your Checkly monitoring checks, current pass/fail status, recent results, alerts, check groups and maintenance windows with BYOK and account id. You bring your own Checkly Checkly user API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Checkly call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.checklyhq.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Checkly rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Checkly receives. The request we make on your behalf, including the key and the arguments, under Checkly's own terms and privacy policy. Checkly acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Checkly gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Checkly data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Checkly (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Checkly at any time to end all access.

Children. Checkly (BYOK) is a general-audience service operated by the adult using the assistant, under Checkly's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Checkly (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Checkly (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Checkly (BYOK) provides: Read your Checkly monitoring checks, current pass/fail status, recent results, alerts, check groups and maintenance windows with BYOK and account id. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Checkly credentials and only access data you are allowed to access. Checkly's terms apply to your use of Checkly; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Checkly. Checkly and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Checkly returns, lightly trimmed; it may be incomplete, delayed or changed by Checkly. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Checkly account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Checkly's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Checkly may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Checkly key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Checkly takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-checkly

Checkly (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Checkly (BYOK) never asks for them.

Get Checkly (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Checkly Checkly user API key. Create one at https://app.checklyhq.com/settings/user/api-keys, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Checkly. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Checkly.