# checkly-mcp

Assertion checks for status, headers and content - no API key.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.2
- **Author:** Unknown
- **License:** MIT
- **npm:** checkly-mcp
- **Source:** https://github.com/mrfentmen/premium-mcps
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 2 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-03T06:28:13.781Z
- **Version scanned:** 1.0.2
- **CVEs:** none found by OSV at scan time

## Tools

12 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `assert_status` — Run a synthetic check on a URL: does it answer with the status you expect, inside the time budget, without a redirect loop.
- `assert_headers` — Check that required headers are present, forbidden ones are absent, or one header contains a given value.
- `assert_content` — Check that a page's HTML contains expected text and does not contain forbidden text — a smoke test for deploys.
- `check_url` — Plain reachability check: HTTP status, response time, server header and any redirects.
- `check_redirects` — Trace every redirect hop with its timing, and flag loops or an http-to-https upgrade that never happens.
- `broken_links` — Read the links on a page and report which ones answer with an error status, so a deploy cannot ship dead links.
- `assert_response_time` — Sample a URL a few times and assert the median and worst time stay inside a budget, reporting each sample.
- `assert_json` — Treat a URL as a JSON API: check it parses, then assert a dot-path exists and optionally equals or contains a value.
- `assert_redirect` — Assert that a URL redirects, optionally that it lands on a given Location and answers with a specific status.
- `http_security_report` — Transport and browser-side security for one URL: HTTPS upgrade, HSTS, CSP, nosniff, referrer and permissions policy, COOP, Secure and HttpOnly cookie flags, and
- `a11y_basics` — The machine-checkable part of an accessibility audit: html lang, document title, single h1 and heading levels, image alt attributes, blank alt text, viewport zo
- `seo_meta` — Search metadata actually served by one URL: title length, meta description, rel=canonical, Open Graph and Twitter card tags, robots meta, hreflang alternates an

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"checkly\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"checkly-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/checkly-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/checkly-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/checkly-mcp
- HTML page: https://forgeregistry.com/registry/checkly-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.