Remote MCP · Endpoint

Upstream MCP server

No. Upstream answered an MCP handshake 14 minutes ago.

UpLast checked 14 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.toolweather/upstream
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
112 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Is this AI/dev API down? Is this model deprecated, what replaces it? Live status for ~40 APIs.
Listing
From the official MCP registry (active).
Recent checks of Upstream
CheckedResultHandshake
14 minutes agoHandshake completed112 ms
9 days agoHandshake completed206 ms
9 days agoHandshake completed79 ms
11 days agoHandshake completed162 ms
12 days agoHandshake completed102 ms
13 days agoHandshake completed84 ms
14 days agoHandshake completed160 ms
14 days agoHandshake completed78 ms
16 days agoHandshake completed387 ms
19 days agoHandshake completed86 ms
21 days agoHandshake completed65 ms
24 days agoHandshake completed91 ms
26 days agoHandshake completed154 ms
28 days agoHandshake completed126 ms

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

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