Remote MCP · Endpoint

Worth MCP server

No. Worth answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://worth.area21.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.a21ai/worth
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
591 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Know what anything is worth, and where to buy or sell it for the best price.
Website
https://worthapp.app/
Repository
https://github.com/a21ai/worth-mcp
Listing
From the official MCP registry (active).
Recent checks of Worth
CheckedResultHandshake
43 minutes agoHandshake completed591 ms
8 days agoHandshake completed529 ms
9 days agoHandshake completed468 ms
11 days agoHandshake completed498 ms
12 days agoHandshake completed487 ms
13 days agoHandshake completed505 ms
14 days agoHandshake completed506 ms
14 days agoHandshake completed493 ms
16 days agoHandshake completed488 ms
19 days agoHandshake completed467 ms
21 days agoHandshake completed573 ms
24 days agoHandshake completed1.07 s

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

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