MyMCPTools
Find MCP servers and check whether they actually respond, via live handshake probes.
Should I use this
Quality & Safety
Findings (1)
- LOWTool 'get_server_history' description lacks action verbin get_server_history
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"mymcptools": {
"url": "https://mymcptools.com/api/mcp"
}
}
}Remote endpoints
https://mymcptools.com/api/mcpstreamable-httpWhat it can do
Tool inventory
Tools (8)
🟢search_mcp_servers(query, category, integration, install_type, official, ...)
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.
Input Schema
{
"type": "object",
"properties": {
"query": {
"description": "Free-text query matched against name, description, author and category.",
"type": "string"
},
"category": {
"description": "Category slug, e.g. 'database'. See list_categories.",
"type": "string"
},
"integration": {
"description": "Integration slug, e.g. 'claude-desktop' or 'cursor'.",
"type": "string"
},
"install_type": {
"description": "Restrict to one install mechanism.",
"type": "string",
"enum": [
"npm",
"pip",
"binary",
"docker",
"source",
"remote"
]
},
"official": {
"description": "Only first-party/official servers.",
"type": "boolean"
},
"only_verified": {
"description": "Only servers whose latest probe verdict is GOOD or WARN.",
"type": "boolean"
},
"limit": {
"description": "Max results (default 10, max 50).",
"type": "integer",
"minimum": 1,
"maximum": 50
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_mcp_server(slug)
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.
Input Schema
{
"type": "object",
"properties": {
"slug": {
"type": "string",
"description": "Catalog slug, e.g. 'filesystem' or 'github'."
}
},
"required": [
"slug"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_server_status(slug)
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.
Input Schema
{
"type": "object",
"properties": {
"slug": {
"description": "Catalog slug. Omit for the catalog-wide verdict rollup.",
"type": "string"
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_server_history(slug, days, limit)
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).
Input Schema
{
"type": "object",
"properties": {
"slug": {
"type": "string",
"description": "Catalog slug."
},
"days": {
"description": "Uptime window width in days (default 14, max 90).",
"type": "integer",
"minimum": 1,
"maximum": 90
},
"limit": {
"description": "Max raw probe points returned (default 30, max 200).",
"type": "integer",
"minimum": 1,
"maximum": 200
}
},
"required": [
"slug"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢list_server_incidents(slug, status, limit)
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'.
Input Schema
{
"type": "object",
"properties": {
"slug": {
"description": "Restrict to one server.",
"type": "string"
},
"status": {
"description": "Restrict by resolution state.",
"type": "string",
"enum": [
"ongoing",
"resolved"
]
},
"limit": {
"description": "Max incidents returned (default 20, max 100).",
"type": "integer",
"minimum": 1,
"maximum": 100
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢list_schema_drift(slug, limit)
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.
Input Schema
{
"type": "object",
"properties": {
"slug": {
"description": "Restrict to one server.",
"type": "string"
},
"limit": {
"description": "Max drift events returned (default 20, max 100).",
"type": "integer",
"minimum": 1,
"maximum": 100
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢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.
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢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.
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Evidence