# MyMCPTools (remote · mymcptools.com)

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

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mymcptools.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/shibley-mymcptools/api-mcp.md), [page](https://verifymcp.io/servers/shibley-mymcptools/api-mcp)

## Channel facts

- Endpoint: `https://mymcptools.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 12417 tokens (~191/item across 65 items; 8 tools + 57 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http shibley-mymcptools https://mymcptools.com/api/mcp
```

### Codex

```toml
[mcp_servers.shibley-mymcptools]
url = "https://mymcptools.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shibley-mymcptools": {
      "type": "remote",
      "url": "https://mymcptools.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shibley-mymcptools --url https://mymcptools.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  shibley-mymcptools:
    url: "https://mymcptools.com/api/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 67, 0)

- [functional regression] Schema quality: 171 → 191
- [functional regression] Resource “LiteLLM” was removed
- [functional regression] Resource “Composio” was removed
- [functional] Schema quality: excellent → good
- [functional] New resource “Composio MCP Server”
- [functional] New resource “LiteLLM MCP Server”

### 2026-08-02 (score 67, +6)

- [functional regression] Resource “Home Assistant MCP” was removed
- [functional improvement] Schema quality: unverified → excellent
- [functional] New resource “Home Assistant MCP Server”

### 2026-08-01 (score 61, −5)

- [functional regression] Schema quality: 140 → 161
- [functional regression] Schema quality: good → unverified

### 2026-07-31 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66)

First indexed and scored.

## MCP tools (8)

### `search_mcp_servers` (~204 tokens)

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. Results carry the live verdict for each server.

Input parameters:

- `category` (string): Category slug, e.g. 'database'. See list_categories.
- `install_type` (string): Restrict to one install mechanism.
- `integration` (string): Integration slug, e.g. 'claude-desktop' or 'cursor'.
- `limit` (integer): Max results (default 10, max 50).
- `official` (boolean): Only first-party/official servers.
- `only_verified` (boolean): Only servers whose latest probe verdict is GOOD or WARN.
- `query` (string): Free-text query matched against name, description, author and category.

### `get_mcp_server` (~73 tokens)

Get one 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.

Input parameters:

- `slug` (string, required): Catalog slug, e.g. 'filesystem' or 'github'.

### `get_server_status` (~88 tokens)

Get live MCP 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.

Input parameters:

- `slug` (string): Catalog slug. Omit for the catalog-wide verdict rollup.

### `get_server_history` (~103 tokens)

Get MCP server uptime 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).

Input parameters:

- `days` (integer): Uptime window width in days (default 14, max 90).
- `limit` (integer): Max raw probe points returned (default 30, max 200).
- `slug` (string, required): Catalog slug.

### `list_server_incidents` (~107 tokens)

List MCP server outage 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'.

Input parameters:

- `limit` (integer): Max incidents returned (default 20, max 100).
- `slug` (string): Restrict to one server.
- `status` (string): Restrict by resolution state.

### `list_schema_drift` (~82 tokens)

List MCP tool-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.

Input parameters:

- `limit` (integer): Max drift events returned (default 20, max 100).
- `slug` (string): Restrict to one server.

### `list_categories` (~50 tokens)

List catalog 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` (~56 tokens)

Get catalog-wide health 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/shibley-mymcptools/api-mcp#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 67
- 2026-08-01: 61
- 2026-07-31: 66
- 2026-07-30: 66

## Links

- Remote endpoint: https://mymcptools.com/api/mcp
- Repository: https://github.com/shibley/mymcptools-mcp-server
- Website: https://mymcptools.com/
- Changelog RSS feed: https://verifymcp.io/servers/shibley-mymcptools/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/shibley-mymcptools/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/shibley-mymcptools/api-mcp