checkly-mcp

MCPcommunity
v1.0.2UnknownMITUpdated 2d agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
563Downloads/wk
2d agoLast update
Package
AuthorUnknown
LicenseMIT
Version1.0.2
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface12 tools · none privileged
Security scan✓ Cleanv1.0.2 · 1d agoHow well does this scan work?
EvalsNone
IndexedOct 3, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

12 tools · none privileged
Statically extracted from the published packagev1.0.2 · 1d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

assert_statusRun a synthetic check on a URL: does it answer with the status you expect, inside the time budget, without a redirect loop.

Run a synthetic check on a URL: does it answer with the status you expect, inside the time budget, without a redirect loop.

No input schema was published for this tool.

assert_headersCheck that required headers are present, forbidden ones are absent, or one header contains a given value.

Check that required headers are present, forbidden ones are absent, or one header contains a given value.

No input schema was published for this tool.

assert_contentCheck that a page's HTML contains expected text and does not contain forbidden text — a smoke test for deploys.

Check that a page's HTML contains expected text and does not contain forbidden text — a smoke test for deploys.

No input schema was published for this tool.

check_urlPlain reachability check: HTTP status, response time, server header and any redirects.

Plain reachability check: HTTP status, response time, server header and any redirects.

No input schema was published for this tool.

check_redirectsTrace every redirect hop with its timing, and flag loops or an http-to-https upgrade that never happens.

Trace every redirect hop with its timing, and flag loops or an http-to-https upgrade that never happens.

No input schema was published for this tool.

broken_linksRead the links on a page and report which ones answer with an error status, so a deploy cannot ship dead links.

Read the links on a page and report which ones answer with an error status, so a deploy cannot ship dead links.

No input schema was published for this tool.

assert_response_timeSample a URL a few times and assert the median and worst time stay inside a budget, reporting each sample.

Sample a URL a few times and assert the median and worst time stay inside a budget, reporting each sample.

No input schema was published for this tool.

assert_jsonTreat a URL as a JSON API: check it parses, then assert a dot-path exists and optionally equals or contains a value.

Treat a URL as a JSON API: check it parses, then assert a dot-path exists and optionally equals or contains a value.

No input schema was published for this tool.

assert_redirectAssert that a URL redirects, optionally that it lands on a given Location and answers with a specific status.

Assert that a URL redirects, optionally that it lands on a given Location and answers with a specific status.

No input schema was published for this tool.

http_security_reportTransport and browser-side security for one URL: HTTPS upgrade, HSTS, CSP, nosniff, referrer and permissions policy, COOP, Secure and HttpOnly cookie flags, and any plain-HTTP resource referenced by the page.

Transport and browser-side security for one URL: HTTPS upgrade, HSTS, CSP, nosniff, referrer and permissions policy, COOP, Secure and HttpOnly cookie flags, and any plain-HTTP resource referenced by the page.

No input schema was published for this tool.

a11y_basicsThe machine-checkable part of an accessibility audit: html lang, document title, single h1 and heading levels, image alt attributes, blank alt text, viewport zoom locking, landmark elements and a skip link.

The machine-checkable part of an accessibility audit: html lang, document title, single h1 and heading levels, image alt attributes, blank alt text, viewport zoom locking, landmark elements and a skip link.

No input schema was published for this tool.

seo_metaSearch metadata actually served by one URL: title length, meta description, rel=canonical, Open Graph and Twitter card tags, robots meta, hreflang alternates and whether every JSON-LD block parses.

Search metadata actually served by one URL: title length, meta description, rel=canonical, Open Graph and Twitter card tags, robots meta, hreflang alternates and whether every JSON-LD block parses.

No input schema was published for this tool.

12 of 12 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
syntheticmonitoringassertionssmoke testlinksmcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-03 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in monitoring & logging