Remote MCP · Endpoint

InsertChat - AI Receptionist MCP server

No. InsertChat - AI Receptionist answered an MCP handshake 3 hours ago.

Up · key neededLast checked 3 hours ago

Server URL

https://api.insertchat.com/v2/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
com.insertchat/insertchat
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
99 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
AI receptionist and AI chatbot: inbox triage, reply drafts, leads, reports, and knowledge training.
Listing
From the official MCP registry (active).
Recent checks of InsertChat - AI Receptionist
CheckedResultHandshake
3 hours agoHandshake completed99 ms
4 days agoHandshake completed455 ms
14 days agoHandshake completed60 ms
15 days agoHandshake completed99 ms
15 days agoHandshake completed140 ms
17 days agoHandshake completed58 ms
18 days agoHandshake completed56 ms
19 days agoHandshake completed86 ms
20 days agoHandshake completed51 ms
21 days agoHandshake completed62 ms
23 days agoHandshake completed195 ms

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

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