Remote MCP · Endpoint

Tolk2Go Interpreter Booking MCP server

No. Tolk2Go Interpreter Booking answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.tolk2go.com/api/v1/mcp

The last check completed an MCP handshake.

Registry name
com.tolk2go/booking
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
500 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Book and manage sworn and qualified interpreters (on-site, phone, video) for a Tolk2Go account.
Listing
From the official MCP registry (active).
Recent checks of Tolk2Go Interpreter Booking
CheckedResultHandshake
1 hour agoHandshake completed500 ms
2 days agoHandshake completed182 ms
4 days agoHandshake completed191 ms
6 days agoHandshake completed158 ms
8 days agoHandshake completed172 ms
10 days agoHandshake completed452 ms
13 days agoHandshake completed465 ms
14 days agoHandshake completed448 ms
16 days agoHandshake completed425 ms
17 days agoHandshake completed362 ms
18 days agoHandshake completed448 ms
21 days agoHandshake completed435 ms
22 days agoHandshake completed447 ms
24 days agoHandshake completed414 ms

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