# MyMCPTools

- Registry name: `io.github.shibley/mymcptools` · version 0.1.1
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security, APIs & integrations, Developer tools, Code & repositories
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): completions, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.shibley%2Fmymcptools
- Server page: https://mcpstation.net/s/io.github.shibley--mymcptools.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://mymcptools.com/api/mcp`

## Tools (as reported by the server, not verified)

- `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 category and integration filter values for catalog searches.
- `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.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html