Remote MCP · Endpoint

MyMCPTools MCP server

Yes, as of 1 hour ago: the check failed for an unclassified reason.

DownLast checked 1 hour ago

Server URL

https://mymcptools.com/api/mcp

The last check failed: the check failed for an unclassified reason.

Registry name
io.github.shibley/mymcptools
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
8 tools
Uptime, last 30 days
55.6% from 18 checks
Described by its publisher as
Find MCP servers and check whether they actually respond, via live handshake probes.
Website
https://mymcptools.com/
Repository
https://github.com/shibley/mymcptools-mcp-server
Listing
From the official MCP registry (active).
Recent checks of MyMCPTools
CheckedResultHandshake
1 hour agoFailed - the check failed for an unclassified reason—
1 day agoFailed - the check failed for an unclassified reason—
2 days agoFailed - the check failed for an unclassified reason—
3 days agoFailed - the check failed for an unclassified reason—
4 days agoFailed - the check failed for an unclassified reason—
5 days agoFailed - the check failed for an unclassified reason—
6 days agoFailed - the check failed for an unclassified reason—
9 days agoFailed - the check failed for an unclassified reason—
11 days agoHandshake completed574 ms
14 days agoHandshake completed577 ms
16 days agoHandshake completed648 ms
18 days agoHandshake completed713 ms
20 days agoHandshake completed665 ms
22 days agoHandshake completed264 ms
24 days agoHandshake completed600 ms
26 days agoHandshake completed574 ms
27 days agoHandshake completed598 ms
29 days agoHandshake completed579 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 21 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with MyMCPTools and makes no claim about it beyond what these checks measured.