INDIVIDUAL MCP TOOL

search_mcp_servers

Search the MyMCPTools catalog of Model Context Protocol servers.

mymcptools.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://mymcptools.com/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for search_mcp_servers and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.mymcptools]
url = "https://mymcptools.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "mymcptools": {
      "type": "http",
      "url": "https://mymcptools.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

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

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "mymcptools": {
      "url": "https://mymcptools.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "mymcptools": {
      "type": "http",
      "url": "https://mymcptools.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "mymcptools",
  "transport": "streamable-http",
  "url": "https://mymcptools.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

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.
get_server_history — Trailing probe history for one server plus a daily uptime sparkline — the reliability signal behind the badge on mymcptools.
list_server_incidents — Reconstructed outage incidents (contiguous runs of failed probes) across the catalog, newest first.
list_schema_drift — Tool-schema and protocol-version drift events detected between successive probes — which servers added, removed or changed tools, and when.
list_categories — Every category and client integration in the MyMCPTools catalog, with the number of servers in each.
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.