Remote MCP · Endpoint

Vocenya Docs MCP server

No. Vocenya Docs answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://vocenya.com/mcp/docs

The last check completed an MCP handshake.

Registry name
com.vocenya/docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
103 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only search over the Vocenya AI receptionist API docs and endpoints, with code samples.
Listing
From the official MCP registry (active).
Recent checks of Vocenya Docs
CheckedResultHandshake
7 hours agoHandshake completed103 ms
4 days agoHandshake completed141 ms
14 days agoHandshake completed108 ms
15 days agoHandshake completed132 ms
15 days agoHandshake completed111 ms
17 days agoHandshake completed116 ms
18 days agoHandshake completed145 ms
19 days agoHandshake completed102 ms
20 days agoHandshake completed113 ms
21 days agoHandshake completed117 ms
23 days agoHandshake completed107 ms
26 days agoHandshake completed145 ms
28 days agoHandshake completed207 ms

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

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