Remote MCP · Endpoint

One Million Tools MCP server

No. One Million Tools answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://tools-empire-mcp.lucas-qin-au.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.lucas-project/one-million-tools
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
739 ms
Tools exposed
42 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
42 free deterministic utilities: JSON, CSV, YAML, encoding, hashing, JWT, cron, formatters, CSS.
Listing
From the official MCP registry (active).
Recent checks of One Million Tools
CheckedResultHandshake
5 hours agoHandshake completed739 ms
3 days agoHandshake completed339 ms
12 days agoHandshake completed324 ms
12 days agoHandshake completed329 ms
14 days agoHandshake completed45 ms
15 days agoHandshake completed581 ms
16 days agoHandshake completed330 ms
17 days agoHandshake completed531 ms
18 days agoHandshake completed342 ms
19 days agoHandshake completed156 ms
22 days agoHandshake completed296 ms
25 days agoHandshake completed672 ms
27 days agoHandshake completed776 ms

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

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.

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