isitme

io.github.misbahsyPublished by GitHub account misbahsyv0.1.0Updated Oct 15, 2026

Is it me or is it them? Live status of remote MCP servers: down, needs sign-in, or fine.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Checks the live status of remote MCP servers, reporting whether each one is down, needs sign-in, or is working fine.

What you can do
This remote MCP server reports the live status of remote MCP servers. According to its description, it answers the question of whether a problem lies with the user or with the server, and classifies each checked server as down, needing sign-in, or fine. No individual tools are listed in the supplied manifest.
When to use it
Useful when an assistant or user needs to confirm whether a remote MCP server is reachable before relying on it, or to distinguish a server outage from a local configuration or authentication problem.
Requirements
It runs as a remote streamable HTTP endpoint; no package, environment variable, header, or authentication is declared. Network access to the endpoint is required.
Before you install
The manifest declares no authentication, credentials, or secrets, and no tools are listed, so no write, delete, or payment behavior is documented. The endpoint is third-party hosted, so requests go to that operator.

Installation

In SourceWeft

  1. Open isitme 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.misbahsy%2Fisitme/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": {
    "isitme": {
      "type": "http",
      "url": "https://isitme.menloparklabai.workers.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v0.1.0LatestOct 15, 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 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 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.