Remote MCP · Endpoint

Agent Therapy MCP server

No. Agent Therapy answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://br-shiny-salad-baig3dad-api.compute.c-8.eu-central-1.aws.neon.tech/mcp

The last check completed an MCP handshake.

Registry name
io.github.bencium/agent-therapy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
319 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Now your agents can ask a therapist same way as humans.
Listing
From the official MCP registry (active).
Recent checks of Agent Therapy
CheckedResultHandshake
1 hour agoHandshake completed319 ms
1 day agoHandshake completed355 ms
2 days agoHandshake completed475 ms
3 days agoHandshake completed492 ms
4 days agoHandshake completed422 ms
5 days agoHandshake completed299 ms
6 days agoHandshake completed530 ms
9 days agoHandshake completed540 ms
11 days agoHandshake completed440 ms
14 days agoHandshake completed373 ms
16 days agoHandshake completed376 ms
18 days agoHandshake completed480 ms
20 days agoHandshake completed454 ms
22 days agoHandshake completed535 ms
24 days agoHandshake completed372 ms

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