Remote MCP · Endpoint

Tolk2Go Interpreter Booking MCP server

No. Tolk2Go Interpreter Booking answered an MCP handshake 6 hours ago.

UpLast checked 6 hours 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
203 ms
Tools exposed
16 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
6 hours agoHandshake completed203 ms
9 days agoHandshake completed174 ms
10 days agoHandshake completed471 ms
11 days agoHandshake completed213 ms
12 days agoHandshake completed163 ms
14 days agoHandshake completed161 ms
14 days agoHandshake completed160 ms
15 days agoHandshake completed145 ms
17 days agoHandshake completed220 ms
19 days agoHandshake completed164 ms
22 days agoHandshake completed500 ms
24 days agoHandshake completed182 ms
26 days agoHandshake completed191 ms
28 days agoHandshake completed158 ms

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

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.