Remote MCP · Endpoint

Vocaneo MCP server

No. Vocaneo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.vocaneo.com/mcp

The last check completed an MCP handshake.

Registry name
com.vocaneo/vocaneo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
262 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
French job profiles, RNCP diplomas and 135,000 training programs. Read-only, no account.
Listing
From the official MCP registry (active).
Recent checks of Vocaneo
CheckedResultHandshake
1 hour agoHandshake completed262 ms
2 days agoHandshake completed385 ms
4 days agoHandshake completed344 ms
5 days agoHandshake completed265 ms
7 days agoHandshake completed266 ms
8 days agoHandshake completed265 ms
9 days agoHandshake completed268 ms
12 days agoHandshake completed265 ms
13 days agoHandshake completed266 ms
15 days agoHandshake completed270 ms
16 days agoHandshake completed277 ms
18 days agoHandshake completed283 ms
19 days agoHandshake completed264 ms
20 days agoHandshake completed262 ms
20 days agoHandshake completed353 ms
21 days agoHandshake completed260 ms
22 days agoHandshake completed271 ms

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

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