MyMCPTools

REMOTE · MYMCPTOOLS.COM · SCANNED AUG 3

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

Available components

67 67 Trust /100

Trust breakdown (6 categories)

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. How we score →

Endpoint Security63

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
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. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability73

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).Pass
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. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management13

Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mymcptools.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 0
- Schema quality: 171 → 191 ▼ functional
- Resource “LiteLLM” was removed ▼ functional
- Resource “Composio” was removed ▼ functional
- Schema quality: excellent → good functional
- New resource “Composio MCP Server” functional
- New resource “LiteLLM MCP Server” functional
2 Aug 26 +6
- Resource “Home Assistant MCP” was removed ▼ functional
- Schema quality: unverified → excellent ▲ functional
- New resource “Home Assistant MCP Server” functional
1 Aug 26 −5
- Schema quality: 140 → 161 ▼ functional
- Schema quality: good → unverified ▼ functional
31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 66

First indexed and scored.

Show 4 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mymcptools.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=mymcptools.com	CN=YR2,O=Let's Encrypt,C=US	30 Jul 2026	28 Oct 2026	RSA 2048	SHA256-RSA	550231701ca2ea01902dbc548e98528e2a3
SANs: mymcptools.com
CN=YR2,O=Let's Encrypt,C=US (CA)	CN=Root YR,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	RSA 2048	SHA256-RSA	4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	RSA 4096	SHA256-RSA	f24b6d17f9d9ad7cb1c9fea78782699f

DNSSEC insecure

Validation of mymcptools.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
mymcptools.com.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=63072000
x-content-type-options	nosniff
x-frame-options	DENY

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mymcptools.com/api/mcp	Verified	200
http (plaintext)	http://mymcptools.com/api/mcp	HTTPS enforced	308	https://mymcptools.com/api/mcp

MCP tools — 8 exposed · ~763 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

get_catalog_stats Get catalog-wide health stats ~56

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 Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_mcp_server Get one MCP server ~73

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 Output Examples

Name	Type	Req	Description
slug	string	yes	Catalog slug, e.g. 'filesystem' or 'github'.

No output schema declared.

No examples provided.

get_server_history Get MCP server uptime history ~103

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 Output Examples

Name	Type	Req	Description
days	integer	—	Uptime window width in days (default 14, max 90).
limit	integer	—	Max raw probe points returned (default 30, max 200).
slug	string	yes	Catalog slug.

No output schema declared.

No examples provided.

get_server_status Get live MCP server status ~88

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 Output Examples

Name	Type	Req	Description
slug	string	—	Catalog slug. Omit for the catalog-wide verdict rollup.

No output schema declared.

No examples provided.

list_categories List catalog categories ~50

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 Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_schema_drift List MCP tool-schema drift ~82

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 Output Examples

Name	Type	Req	Description
limit	integer	—	Max drift events returned (default 20, max 100).
slug	string	—	Restrict to one server.

No output schema declared.

No examples provided.

list_server_incidents List MCP server outage incidents ~107

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 Output Examples

Name	Type	Req	Description
limit	integer	—	Max incidents returned (default 20, max 100).
slug	string	—	Restrict to one server.
status	string	—	Restrict by resolution state.

No output schema declared.

No examples provided.

search_mcp_servers Search MCP servers ~204

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 Output Examples

Name	Type	Req	Description
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.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

30 Jul 3 Aug