Remote MCP · Endpoint

Smartwebchat MCP server

No. Smartwebchat answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://smartwebchat.eu/api/mcp

The last check completed an MCP handshake.

Registry name
eu.smartwebchat/chatbots
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
316 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Create and manage website chatbots for European SMBs: bots, chat, and captured leads.
Listing
From the official MCP registry (active).
Recent checks of Smartwebchat
CheckedResultHandshake
6 hours agoHandshake completed316 ms
9 days agoHandshake completed318 ms
10 days agoHandshake completed311 ms
11 days agoHandshake completed315 ms
12 days agoHandshake completed322 ms
14 days agoHandshake completed312 ms
15 days agoHandshake completed315 ms
15 days agoHandshake completed315 ms
17 days agoHandshake completed308 ms
19 days agoHandshake completed322 ms
22 days agoHandshake completed306 ms
24 days agoHandshake completed314 ms
26 days agoHandshake completed330 ms
28 days agoHandshake completed314 ms

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

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