Remote MCP · Endpoint

AVATALKS MCP server

No. AVATALKS answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://avatalks.app/mcp

The last check completed an MCP handshake.

Registry name
app.avatalks/avatalks
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
123 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI personas you can talk to: a public arena of speaking, arguing characters, hosted at avatalks.app.
Listing
From the official MCP registry (active).
Recent checks of AVATALKS
CheckedResultHandshake
6 hours agoHandshake completed123 ms
9 days agoHandshake completed132 ms
10 days agoHandshake completed130 ms
11 days agoHandshake completed119 ms
12 days agoHandshake completed111 ms
14 days agoHandshake completed140 ms
14 days agoHandshake completed130 ms
15 days agoHandshake completed115 ms
17 days agoHandshake completed116 ms
19 days agoHandshake completed149 ms
22 days agoHandshake completed112 ms
24 days agoHandshake completed129 ms
26 days agoHandshake completed146 ms
28 days agoHandshake completed116 ms

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

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