Remote MCP · Endpoint

in.therapistsnearme/directory MCP server

No. in.therapistsnearme/directory answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.therapistsnearme.in/api/mcp

The last check completed an MCP handshake.

Registry name
in.therapistsnearme/directory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
673 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search India's credential-verified therapist directory: read-only, public, checkable registrations.
Listing
From the official MCP registry (active).
Recent checks of in.therapistsnearme/directory
CheckedResultHandshake
1 hour agoHandshake completed673 ms
7 hours agoHandshake completed806 ms
2 days agoHandshake completed653 ms
4 days agoHandshake completed656 ms
6 days agoHandshake completed643 ms
9 days agoHandshake completed674 ms
11 days agoHandshake completed687 ms
13 days agoHandshake completed698 ms
15 days agoHandshake completed704 ms
17 days agoHandshake completed714 ms
19 days agoHandshake completed692 ms
21 days agoHandshake completed687 ms
23 days agoHandshake completed694 ms
24 days agoHandshake completed1.15 s

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

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