mcpbeat

MyMCPTools MCP Server

io.github.shibley/mymcptools
not responding

MyMCPTools is listed as active in the registry but did not answer our last check. It exposes 8 tools. Last commit 30 Jul 2026.

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

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
0.0%
Uptime 24h
0 of 92 checks
8
Tools
read from the server
83 ms
Response time
average over 24h
0
Stars
last commit 30 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add mymcptools --transport http https://mymcptools.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mymcptools": {
      "url": "https://mymcptools.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mymcptools]
url = "https://mymcptools.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mymcptools": {
      "url": "https://mymcptools.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mymcptools": {
      "url": "https://mymcptools.com/api/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

server
get_server_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).
get_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.
list_server_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'.
mcp
get_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.
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.
catalog
get_catalog_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.
categories
list_categories
Every category and client integration in the MyMCPTools catalog, with the number of servers in each. The slugs returned here are the valid values for the category and integration filters on search_mcp_servers.
schema
list_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.

Endpoints

URLTransportStateLatencyChecked
https://mymcptools.com/api/mcp streamable-http answering 83 ms 2 min ago

MyMCPTools — questions

Answers built from our own checks of this server.

What can MyMCPTools do?
It exposes 8 tools, read directly from the server on our last check. Among them: get_catalog_stats, get_mcp_server, get_server_history, get_server_status, list_categories, list_schema_drift and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is MyMCPTools mostly used for?
Its tools cluster around server and mcp. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is MyMCPTools working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 83 ms. The bar chart above shows every period we have measured.
The registry lists MyMCPTools as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect MyMCPTools?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does MyMCPTools need an API key?
No. MyMCPTools completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
Is MyMCPTools open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.