Remote MCP · Endpoint

The River MCP server

No. The River answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://theriver.markets/mcp

The last check completed an MCP handshake.

Registry name
markets.theriver/the-river
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
532 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Tokenized US stocks onchain: listings, holdings, US prices, pre-filled trade links. Read-only.
Website
https://theriver.markets/agents
Listing
From the official MCP registry (active).
Recent checks of The River
CheckedResultHandshake
1 hour agoHandshake completed532 ms
1 day agoHandshake completed1.21 s
4 days agoHandshake completed542 ms
7 days agoHandshake completed534 ms
9 days agoHandshake completed572 ms
11 days agoHandshake completed558 ms
13 days agoHandshake completed542 ms
15 days agoHandshake completed540 ms
17 days agoHandshake completed492 ms
19 days agoHandshake completed697 ms
21 days agoHandshake completed521 ms
22 days agoHandshake completed596 ms
23 days agoHandshake completed560 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.

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