MyMCPTools
REMOTE · MYMCPTOOLS.COM
Find MCP servers and check whether they actually respond, via live handshake probes.
Available components
Last scanned (15 hours ago)
Scores higher than 7% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 429. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 13 Nov 26 0
- Endpoint reachability: unreachable → not serving MCP ▼ security
- HSTS header: unverified → fail ▼ security
- TLS certificate: unverified → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 429. security
- 12 Nov 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 6 Nov 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
- 25 Oct 26 −65
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 24 Oct 26 0
- Tool “list_categories” rewrote its description, which is the text the model reads security
- “search_mcp_servers” reworded the description of “category” cosmetic
- 28 Sept 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
- 25 Sept 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
- 10 Sept 26 0
- New resource “Coinrule MCP” 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 Nov 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 Sept 2026 | 29 Dec 2026 | RSA 2048 | SHA256-RSA | 6db1eaca327b0624910f049d8f2073b1910 |
| 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. | DS published | 19718 | 13 | Verified |
| mymcptools.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 429 |
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 | HTTP error | 429 | |
| 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 ~46
Every category and client integration in the MyMCPTools catalog, with the number of servers in each. The slugs returned here are the valid category and integration filter values for catalog searches.
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 ~205
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' or 'devops'. |
| 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.
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'
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 23 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 760 tokens of context every time the server is loaded.
Does the MyMCPTools MCP server require authentication?
Its publisher declares no required credentials for MyMCPTools. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the MyMCPTools MCP server still maintained?
MyMCPTools is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the MyMCPTools MCP server?
VerifyMCP ran 5 checks on MyMCPTools, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about MyMCPTools: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.