MCP.Market

MyMCPTools MCP server

online · 100% uptime
by shibley·io.github.shibley/mymcptools·v0.1.1
No reviews yet

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

A87/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A87/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed MyMCPTools yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

MyMCPTools tools (8)

write = sends, deletes, buys or posts
  • get_catalog_statsFree

    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.

  • get_mcp_serverFree

    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.

  • get_server_historyFree

    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).

  • get_server_statusFree

    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.

  • list_categoriesFree

    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.

  • list_schema_driftFree

    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.

  • list_server_incidentsFree

    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'.

  • search_mcp_serversFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1309ms20/20
  • Tool poisoning8 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 56 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 87/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How MyMCPTools compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 73% of 48,255 servers
Tools
8
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
35 ms
faster than 94% of 30,031 servers

What its tools let an agent do: 8 read

Install MyMCPTools in Claude Code, Cursor or VS Code

claude mcp add --transport http mymcptools https://mymcptools.com/api/mcp
Add to Cursor

What the publisher says

From the MyMCPTools repository's README, as published. We do not edit it. Read it on GitHub

MyMCPTools MCP Server

An MCP server for finding other MCP servers — and, more usefully, for checking whether the one you are about to recommend is actually reachable.

Every uptime figure it returns comes from a real MCP handshake against the server's remote endpoint, not from self-reported metadata in a README.

Backed by mymcptools.com. No API key required.

Install

Remote endpoint (recommended — nothing to install)

The server is hosted. If your client speaks Streamable HTTP, point it straight at:

https://mymcptools.com/api/mcp

Stateless, read-only, no auth, no API key. This is also the entry published to the official MCP Registry as io.github.shibley/mymcptools.

Local stdio adapter

The code in this repo is a thin stdio adapter over that same endpoint, for clients that don't speak Streamable HTTP yet. It is not on npm yet, so build it from source (Node.js 18+):

git clone https://github.com/shibley/mymcptools-mcp-server.git
cd mymcptools-mcp-server
npm install && npm run build

Then point your client at the built entrypoint:

{
  "mcpServers": {
    "mymcptools": {
      "command": "node",
      "args": ["/absolute/path/to/mymcptools-mcp-server/dist/index.js"]
    }
  }
}

Add that to claudedesktopconfig.json (Claude Desktop), .cursor/mcp.json (Cursor), or your client's equivalent.

Set MYMCPTOOLSMCPURL to override the upstream endpoint the adapter talks to.

Tools

What the probe data does and does not cover

Worth stating plainly, because the numbers are easy to misread:

  • The catalog carries ~2,700 entries, but only ~44 are probeable — that is, they publish a remote endpoint something can actually connect to.
  • The rest are local-only servers (stdio, run via npx or docker on your machine). There is no remote endpoint to handshake against, so they are reported as UNPROBEABLE rather than assigned a made-up status. For those, getmcpserver falls back to a static repo-freshness signal.
  • UNPROBEABLE therefore means "not remotely checkable", not "broken".

So treat the live-verification tools as high-confidence for remote/hosted servers, and treat the catalog entry itself as the useful part for local ones.

Verdicts

Development

npm install
npm run build

Smoke-test the built server over stdio:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

MyMCPTools: common questions

Is MyMCPTools MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the MyMCPTools safety report
How do I install MyMCPTools?
It runs remotely at mymcptools.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does MyMCPTools need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is MyMCPTools maintained?
The last commit was 97 days ago (2026-07-30). The latest release is v0.1.1.
Is MyMCPTools up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of MyMCPTools?
Servers from other publishers that do the same job: Contact Affordance MCP server and Business Contact Finder MCP server.
How does MyMCPTools compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to MyMCPTools

Same job from other publishers: the closest match first, then the best rated.

  • Contact Affordance
    Check how to contact a business website, and whether that contact path actually works.
    A
  • Business Contact Finder
    Check how to contact a business website, and whether that contact path actually works.
    A

More from shibley →