Connect-MCP

MyMCPTools

io.github.shibley/mymcptools · v0.1.1

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

MCPremoteno credentials

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 8 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

A 92/100

What it does: 8 tools · 8 read, 0 write · Developer tools

Test call list_server_incidents: worked (945 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +2
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +20
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://mymcptools.com/api/mcp

Tools

8 tools listed at last check
  • 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.
  • 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.
  • 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.
  • 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).
  • 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'.
  • 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.
  • 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.
  • 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.

Badge

Connect-MCP badge for io.github.shibley/mymcptools

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.shibley/mymcptools.svg)](https://clawy.uk/mcp/s/io.github.shibley/mymcptools)

Repository · Website