Statuscake Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.3Updated Oct 25, 2026

Uptime, TCP port, SSL chain and DNS propagation checks - no API key.

VerifiedSTDIODesktop onlyWeb Search & Scraping Cloud & Infrastructure Security & Monitoring

Server details

Identifier: io.github.mrfentmen/statuscake-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 23, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account mrfentmen for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.mrfentmen%2Fstatuscake-mcp.svg)](https://sourceweft.com/mcp/io.github.mrfentmen%2Fstatuscake-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server for uptime, TCP port, SSL chain and DNS propagation checks, letting an assistant run connectivity diagnostics on your behalf.

What you can do: Run uptime checks against a site to see whether it responds. Check whether a given TCP port on a host is open. Inspect an SSL certificate chain for validity. Look up DNS propagation to see whether resolution has taken effect.
When to use it: Use it when you want an assistant to quickly check whether a site or host is reachable, a TCP port is open, an SSL chain is valid, or DNS has propagated. Suited to quick connection troubleshooting rather than long-term monitoring.
Requirements: Installed as an npm package and run as a local process over stdio, so it needs a Node.js runtime on the machine. Desktop only; it cannot run in a browser.

Before you install

Checks make network requests to external targets, so the hostnames and addresses you test are sent to third-party services. The registry declares no authentication or environment variables; confirm what configuration is actually needed before installing.

Installation

In SourceWeft

Open Statuscake Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.3LatestOct 2, 2026
v1.0.0Sep 23, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.