Remote MCP · Endpoint

com.lobbyvoices/receptionist-toolkit MCP server

No. com.lobbyvoices/receptionist-toolkit answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://lobbyvoices.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.lobbyvoices/receptionist-toolkit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
556 ms
Tools exposed
8 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
Free receptionist tools: phone scripts, IVR menus (EN+ES), ElevenLabs prompts, missed-call math
Listing
From the official MCP registry (active).
Recent checks of com.lobbyvoices/receptionist-toolkit
CheckedResultHandshake
2 hours agoHandshake completed556 ms
1 day agoHandshake completed556 ms
2 days agoHandshake completed577 ms
3 days agoHandshake completed547 ms
4 days agoHandshake completed544 ms
5 days agoHandshake completed585 ms
7 days agoHandshake completed686 ms
9 days agoHandshake completed603 ms
12 days agoHandshake completed543 ms
14 days agoHandshake completed564 ms
16 days agoHandshake completed542 ms
18 days agoHandshake completed533 ms
20 days agoHandshake completed538 ms
23 days agoFailed - the request timed out—
25 days agoHandshake completed540 ms
26 days agoHandshake completed562 ms
28 days agoHandshake completed587 ms
29 days agoHandshake completed484 ms

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

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 com.lobbyvoices/receptionist-toolkit and makes no claim about it beyond what these checks measured.