Remote MCP · Endpoint

Toolweather MCP server

No. Toolweather answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://toolweather.toolweather.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.toolweather/toolweather
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
129 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
MCP health (~2k servers) + API status & model deprecations (~40 APIs). One suite for agents.
Listing
From the official MCP registry (active).
Recent checks of Toolweather
CheckedResultHandshake
2 hours agoHandshake completed129 ms
19 hours agoHandshake completed73 ms
2 days agoHandshake completed66 ms
3 days agoHandshake completed89 ms
4 days agoHandshake completed69 ms
5 days agoHandshake completed82 ms
6 days agoHandshake completed114 ms
7 days agoHandshake completed75 ms
10 days agoHandshake completed66 ms
13 days agoHandshake completed61 ms
15 days agoHandshake completed54 ms
17 days agoHandshake completed85 ms
19 days agoHandshake completed60 ms
21 days agoHandshake completed54 ms

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

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 Toolweather and makes no claim about it beyond what these checks measured.