uptimerobot-mcp

MCPcommunity
v1.0.4UnknownMITUpdated 2d agonpmGitHub

Uptime, port, TLS and DNS checks for any site - 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 →
510Downloads/wk
2d agoLast update
Package
AuthorUnknown
LicenseMIT
Version1.0.4
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 surface8 tools · none privileged
Security scan✓ Cleanv1.0.4 · todayHow 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

8 tools · none privileged
Statically extracted from the published packagev1.0.4 · 14h 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.

check_urlIs a page up right now: HTTP status, response time, server, redirect chain and the first text on the page.

Is a page up right now: HTTP status, response time, server, redirect chain and the first text on the page.

No input schema was published for this tool.

check_endpointsUp/down sweep of up to 10 URLs in one call, with status code and response time for each.

Up/down sweep of up to 10 URLs in one call, with status code and response time for each.

No input schema was published for this tool.

port_monitorCheck whether TCP ports on a host accept connections, with the service usually found on each port.

Check whether TCP ports on a host accept connections, with the service usually found on each port.

No input schema was published for this tool.

ssl_expiryDays left on a site's TLS certificate, who issued it and whether the chain is trusted.

Days left on a site's TLS certificate, who issued it and whether the chain is trusted.

No input schema was published for this tool.

dns_healthA, AAAA, NS, MX, TXT and CAA records for a domain, plus whether SPF is published.

A, AAAA, NS, MX, TXT and CAA records for a domain, plus whether SPF is published.

No input schema was published for this tool.

monitor_reportOne call that runs the whole monitor sweep on a URL: reachability, TLS certificate and DNS, with a verdict.

One call that runs the whole monitor sweep on a URL: reachability, TLS certificate and DNS, with a verdict.

No input schema was published for this tool.

multi_region_checkRequests the same URL from several countries at once and reports each node's country, city, network, HTTP status and response time, so a fault that only affects one region is visible. Complements a single-vantage-point check.

Requests the same URL from several countries at once and reports each node's country, city, network, HTTP status and response time, so a fault that only affects one region is visible. Complements a single-vantage-point check.

No input schema was published for this tool.

vendor_uptimeHow UptimeRobot's own services have been behaving, from its public status board: every published monitor with its overall, 30-day and 90-day uptime ratios, the days that were not a clean 100%, and the current up/down counts.

How UptimeRobot's own services have been behaving, from its public status board: every published monitor with its overall, 30-day and 90-day uptime ratios, the days that were not a clean 100%, and the current up/down counts.

No input schema was published for this tool.

8 of 8 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

Uptime, port, TLS and DNS checks for any site - no API key.

Keywords
uptimemonitoringportsssldnsmcp
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