MyMCPTools

io.github.shibleyPublished by GitHub account shibleyv0.1.1Updated Oct 24, 2026

Find MCP servers and check whether they actually respond, via live handshake probes.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A hosted, read-only MCP server for searching an MCP server catalog and checking whether listed servers actually respond to live handshake probes.

What you can do
  • Search the catalog of MCP servers by keyword, category, client integration, install type or official status, and list categories and integrations with counts.
  • Read a full entry for one server: description, author, install command, repo, supported clients and current probe verdict.
  • Check live status for one server or the whole catalog: verdict, tool count, handshake latency, protocol version and last healthy time.
  • Review probe history with a daily uptime sparkline, and list reconstructed outage incidents.
  • Track tool-schema and protocol-version drift between probes, and get population-level catalog health statistics.
When to use it
Useful when choosing which MCP server to add and wanting evidence that a remote server is reachable, or when monitoring a server you already depend on for outages and breaking tool changes. Also handy for browsing the catalog by category or client.
Requirements
Remote Streamable HTTP endpoint at mymcptools.com; no API key or authentication. A local stdio adapter exists but is not published to npm, so it must be built from source with Node.js 18+; the MYMCPTOOLS_MCP_URL variable overrides the upstream endpoint.
Before you install
Read-only and stateless, with no credentials requested. Probe verdicts only cover remote endpoints: most catalog entries are local-only and reported as UNPROBEABLE, which means not remotely checkable rather than broken. Uptime and drift data reflect the operator's own probing, not independent verification.

Installation

In SourceWeft

  1. Open MyMCPTools 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.shibley%2Fmymcptools/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": {
    "mymcptools": {
      "type": "http",
      "url": "https://mymcptools.com/api/mcp"
    }
  }
}

README

MyMCPTools MCP Server

An MCP server for finding other MCP servers — and, more usefully, for checking whether the one you are about to recommend is actually reachable.

Every uptime figure it returns comes from a real MCP handshake against the server's remote endpoint, not from self-reported metadata in a README.

Backed by mymcptools.com. No API key required.

Install

Remote endpoint (recommended — nothing to install)

The server is hosted. If your client speaks Streamable HTTP, point it straight at:

https://mymcptools.com/api/mcp

Stateless, read-only, no auth, no API key. This is also the entry published to the official MCP Registry as io.github.shibley/mymcptools.

Local stdio adapter

The code in this repo is a thin stdio adapter over that same endpoint, for clients that don't speak Streamable HTTP yet. It is not on npm yet, so build it from source (Node.js 18+):

bash
git clone https://github.com/shibley/mymcptools-mcp-server.gitcd mymcptools-mcp-servernpm install && npm run build

Then point your client at the built entrypoint:

json
{  "mcpServers": {    "mymcptools": {      "command": "node",      "args": ["/absolute/path/to/mymcptools-mcp-server/dist/index.js"]    }  }}

Add that to claude_desktop_config.json (Claude Desktop), .cursor/mcp.json (Cursor), or your client's equivalent.

Set MYMCPTOOLS_MCP_URL to override the upstream endpoint the adapter talks to.

Tools

ToolWhat it answers
search_mcp_serversWhich servers match this keyword, category, client integration or install type?
get_mcp_serverFull entry for one server: install command, repo, supported clients, current probe verdict.
get_server_statusIs this server reachable right now? Verdict, exposed tool count, handshake latency, negotiated protocol version.
get_server_historyTrailing probe history and a daily uptime sparkline for one server.
list_server_incidentsReconstructed outages — contiguous runs of failed probes, with start, end and duration.
list_schema_driftWhich servers added, removed or changed tools between probes. Useful for spotting breaking changes.
list_categoriesEvery category and client integration, with counts. Returns the valid slugs for the filters above.
get_catalog_statsPopulation-level health: verdict breakdown, transport mix, latency percentiles.

What the probe data does and does not cover

Worth stating plainly, because the numbers are easy to misread:

  • The catalog carries ~2,700 entries, but only ~44 are probeable — that is, they publish a remote endpoint something can actually connect to.
  • The rest are local-only servers (stdio, run via npx or docker on your machine). There is no remote endpoint to handshake against, so they are reported as UNPROBEABLE rather than assigned a made-up status. For those, get_mcp_server falls back to a static repo-freshness signal.
  • UNPROBEABLE therefore means "not remotely checkable", not "broken".

So treat the live-verification tools as high-confidence for remote/hosted servers, and treat the catalog entry itself as the useful part for local ones.

Verdicts

VerdictMeaning
GOODHandshake succeeded and the server listed its tools.
WARNReachable, but something was off — slow handshake or a degraded response.
AUTH_REQUIREDEndpoint is live but needs credentials before it will list tools.
DOWNEndpoint is published but the handshake failed.
UNPROBEABLENo remote endpoint to probe — typically a local stdio server.

Development

bash
npm installnpm run build

Smoke-test the built server over stdio:

bash
printf '%s\n%s\n%s\n' \  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"t","version":"1"}}}' \  '{"jsonrpc":"2.0","method":"notifications/initialized"}' \  '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \  | node dist/index.js

License

MIT

Source: README.md at commit 9159ce4

Tools

8

search_mcp_servers

Search MCP servers

Search the MyMCPTools catalog of Model Context Protocol servers. Filter by free-text query, category slug, integration slug (claude-desktop, cursor, vs-code, ...), install type, or official status. Set only_verified to restrict to servers that answered a live MCP handshake on the most recent probe. Results carry the live verdict for each server.

Parameterslimitquerycategoryofficialintegrationinstall_typeonly_verified

get_mcp_server

Get one MCP server

Full catalog entry for one MCP server by slug: description, author, install command, repo, supported clients, current probe verdict, static repo-freshness signal for local servers, and related servers in the same categories.

Parametersslugrequired

get_server_status

Get live MCP server status

Current live-probe status for one server: verdict (GOOD / WARN / AUTH_REQUIRED / DOWN / UNPROBEABLE), exposed tool count, handshake latency, negotiated protocol version, remote endpoint, and when it was last seen healthy. Omit the slug to get the catalog-wide verdict summary instead.

Parametersslug

get_server_history

Get MCP server uptime history

Trailing probe history for one server plus a daily uptime sparkline — the reliability signal behind the badge on mymcptools.com. Returns per-day uptime buckets and the raw probe points (timestamp, verdict, latency).

Parametersdaysslugrequiredlimit

list_server_incidents

List MCP server outage incidents

Reconstructed outage incidents (contiguous runs of failed probes) across the catalog, newest first. Each incident has a start, an end (or ongoing), a duration and the failure reason. Filter to one server with slug, or to open outages with status='ongoing'.

Parameterssluglimitstatus

list_schema_drift

List MCP tool-schema drift

Tool-schema and protocol-version drift events detected between successive probes — which servers added, removed or changed tools, and when. Use this to spot breaking changes in a server you depend on. Newest first.

Parameterssluglimit

list_categories

List catalog categories

Every category and client integration in the MyMCPTools catalog, with the number of servers in each. The slugs returned here are the valid category and integration filter values for catalog searches.

Takes no parameters.

get_catalog_stats

Get catalog-wide health stats

Aggregate health of the whole MCP population: verdict breakdown, share of probeable servers actually serving, transport mix, handshake latency percentiles, tool counts and probe freshness. This is the 'how healthy is MCP right now?' headline number.

Takes no parameters.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

100% 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
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts