Uptime Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Check website availability, latency, and TLS certificate expiry locally. No key required.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Lets an assistant check whether websites are reachable, measure their latency, and inspect TLS certificate expiry from the local machine.

What you can do
This local MCP server gives an assistant tools for website availability checks, latency measurement, and TLS certificate expiry inspection. Checks run locally on the user's machine rather than through a hosted service. The manifest does not list individual tool names, so the exact tool set is not documented here.
When to use it
Useful when you want an assistant to verify that a site or endpoint is up, compare response times, or warn about a certificate nearing expiry during development or operations work. It is a lightweight option when you would rather not sign up for a hosted uptime service.
Requirements
Runs as a local process over stdio, installed from the npm package uptime-mcp, so Node.js and npm are needed. No API key, account, environment variable, or header is declared. Network access is required to reach the sites being checked. Desktop only.
Before you install
The server makes outbound network requests to whatever hosts you ask it to check, so those hostnames are visible to the network and to the target sites. No credentials are requested. It only reads availability, latency, and certificate data; no write, send, or delete actions are described.

Installation

In SourceWeft

  1. Open Uptime Mcp in the dashboard and add it to a workspace.
  2. 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

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

Version history

1
  1. v1.0.0LatestSep 22, 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.