Remote MCP · Endpoint

Amfion front desk setup MCP server

No. Amfion front desk setup answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://api.amfionhq.com/v1/setup/mcp

The last check completed an MCP handshake.

Registry name
com.amfionhq/front-desk-setup
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
290 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Build and test an AI front desk for a service business from its website, before signing up.
Listing
From the official MCP registry (active).
Recent checks of Amfion front desk setup
CheckedResultHandshake
53 minutes agoHandshake completed290 ms
3 days agoHandshake completed392 ms
12 days agoHandshake completed406 ms
13 days agoHandshake completed312 ms
15 days agoHandshake completed308 ms
15 days agoHandshake completed345 ms
17 days agoHandshake completed360 ms
18 days agoHandshake completed302 ms
18 days agoHandshake completed325 ms
20 days agoHandshake completed295 ms
22 days agoHandshake completed315 ms
25 days agoHandshake completed300 ms
27 days agoHandshake completed303 ms
29 days agoHandshake completed300 ms

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

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