Developer Tools

mymcptools.com

Searches and monitors MCP servers by providing catalog entries, status, history, and incident data from MyMCPTools.

1 endpoint8 known toolsFirst detected July 31, 2026Last detected August 31, 2026

ENDPOINT 1

https://mymcptools.com/api/mcp

No auth detected

MCP server metadata

Name: mymcptools
Version: 1.0.0

Capabilities

tools.listChangedresources.listChangedcompletions

Server instructions

MyMCPTools is a live-verified directory of Model Context Protocol servers. Use search_mcp_servers to discover servers by keyword, category or integration, get_mcp_server for full install details on one server, and get_server_status / get_server_history / list_server_incidents to check whether a server is actually reachable before recommending it. Every uptime figure comes from real MCP handshakes against the server's remote endpoint, not from self-reported metadata.

Known tools 8

search_mcp_servers

Search the MyMCPTools catalog of Model Context Protocol servers.

Inferred read-only

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.

Potential side effects

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.

Inferred read-only

get_server_history

Trailing probe history for one server plus a daily uptime sparkline — the reliability signal behind the badge on mymcptools.

Inferred read-only

list_server_incidents

Reconstructed outage incidents (contiguous runs of failed probes) across the catalog, newest first.

Inferred read-only

list_schema_drift

Tool-schema and protocol-version drift events detected between successive probes — which servers added, removed or changed tools, and when.

Inferred read-only

list_categories

Every category and client integration in the MyMCPTools catalog, with the number of servers in each.

Inferred read-only

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

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.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for mymcptools.com was fetched 2026-08-03T18:13:04.233Z and is being refreshed.

Trust status New

This domain appears to have previously been parked, so its current status is new or unverified.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.