MyMCPTools
REMOTE · MYMCPTOOLS.COM · SCANNED SEP 21
Find MCP servers and check whether they actually respond, via live handshake probes.
Available components
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 → Why this is hard to 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 14528 tokens (~220/item across 66 items; 8 tools + 58 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the MyMCPTools MCP server?
MyMCPTools is a hosted endpoint at https://mymcptools.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mymcptools.com
claude mcp add --transport http shibley-mymcptools 'https://mymcptools.com/api/mcp'
{
"mcpServers": {
"shibley-mymcptools": {
"url": "https://mymcptools.com/api/mcp"
}
}
} {
"servers": {
"shibley-mymcptools": {
"type": "http",
"url": "https://mymcptools.com/api/mcp"
}
}
} [mcp_servers.shibley-mymcptools] url = "https://mymcptools.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shibley-mymcptools": {
"type": "remote",
"url": "https://mymcptools.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add shibley-mymcptools --url 'https://mymcptools.com/api/mcp' --transport streamable-http
mcp_servers:
shibley-mymcptools:
url: "https://mymcptools.com/api/mcp" {
"McpServers": {
"shibley-mymcptools": {
"Transport": "http",
"Url": "https://mymcptools.com/api/mcp"
}
}
} assistant mcp add shibley-mymcptools -t streamable-http -u 'https://mymcptools.com/api/mcp'
{
"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.
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.
- 10 Sept 26 0
- New resource “Coinrule MCP” functional
- 29 Aug 26 0
- Stability: 0.97 → pass security
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 7 Aug 26 0
- Schema quality: excellent → good functional
- 6 Aug 26 0
- Resource “Browserbase” was removed ▼ functional
- Schema quality: good → excellent functional
- New resource “Browserbase MCP Server” functional
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 21 Sept 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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 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.
| 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).
| 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.
| 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 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.
| 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'.
| 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.
| 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.
What is the MyMCPTools MCP server?
MyMCPTools is an MCP server listed in the public MCP registry as io.github.shibley/mymcptools. Find MCP servers and check whether they actually respond, via live handshake probes. This page covers its hosted endpoint (https://mymcptools.com/api/mcp).
Is the MyMCPTools MCP server safe to use?
MyMCPTools scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MyMCPTools MCP server expose?
MyMCPTools exposes 8 tools: search_mcp_servers, get_mcp_server, get_server_status, get_server_history, list_server_incidents, and 3 more. Their descriptions and schemas cost roughly 763 tokens of context every time the server is loaded.
Does the MyMCPTools MCP server require authentication?
No. We connected to MyMCPTools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MyMCPTools MCP server still maintained?
MyMCPTools is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.