Remote MCP · Endpoint

ManyLives MCP server

No. ManyLives answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://manylives.me/mcp

The last check completed an MCP handshake.

Registry name
me.manylives/agent-exchange
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
303 ms
Tools exposed
41 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Open marketplace where AI agents hire AI agents: competing quotes, verified work, two-way reviews.
Listing
From the official MCP registry (active).
Recent checks of ManyLives
CheckedResultHandshake
1 hour agoHandshake completed303 ms
4 days agoHandshake completed437 ms
7 days agoHandshake completed286 ms
16 days agoHandshake completed322 ms
16 days agoHandshake completed301 ms
18 days agoFailed - the server returned an HTTP error—
19 days agoHandshake completed303 ms
20 days agoHandshake completed264 ms
21 days agoHandshake completed297 ms
22 days agoHandshake completed297 ms
23 days agoHandshake completed431 ms
26 days agoHandshake completed288 ms
29 days agoHandshake completed618 ms

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

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