MCP Registry Validator — Check Endpoints Actually Resolve

io.github.operatorsheetsPublished by GitHub account operatorsheetsv0.2.1Updated Oct 24, 2026

Check an MCP endpoint resolves: liveness, live tool list, schema drift. Free.

The publisher's own server: Resolve

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Checks whether an MCP endpoint is reachable, lists its live tools, and reports schema drift over time.

What you can do
This remote MCP server lets an assistant verify that another MCP endpoint actually resolves. According to its description, it checks liveness, retrieves the live tool list, and detects schema drift. It is described as free to use.
When to use it
Useful when you want to confirm an MCP server is up before relying on it, or to notice when its tool definitions change between checks. It is aimed at endpoint health and tool-schema monitoring rather than general tasks.
Requirements
A remote streamable HTTP endpoint at No authentication, environment variables, or headers are declared, and no local package is needed. Network access to the endpoint is required.
Before you install
The manifest declares no authentication, so treat anything you send as unauthenticated. The description does not state what endpoint details are stored or shared, so avoid submitting sensitive endpoint URLs or credentials.

Installation

In SourceWeft

  1. Open MCP Registry Validator — Check Endpoints Actually Resolve in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.operatorsheets%2Fmcp-uptime/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "registry-validator-check-endpoints-actua": {
      "type": "http",
      "url": "https://mcp-uptime.theopslog.workers.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Resolve integrations