Remote MCP · Endpoint

Final POS – Custom POS Builder MCP server

No. Final POS – Custom POS Builder answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://ai.finalpos.com/mcp

The last check completed an MCP handshake.

Registry name
com.finalpos/final
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
81 ms
Tools exposed
177 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Build custom POS apps with any AI agent: checkout flows, kiosks, payment terminals. Plus store ops.
Listing
From the official MCP registry (active).
Recent checks of Final POS – Custom POS Builder
CheckedResultHandshake
17 minutes agoHandshake completed81 ms
9 days agoHandshake completed84 ms
9 days agoHandshake completed81 ms
11 days agoHandshake completed86 ms
12 days agoHandshake completed127 ms
13 days agoHandshake completed93 ms
14 days agoHandshake completed190 ms
14 days agoHandshake completed77 ms
16 days agoHandshake completed100 ms
19 days agoHandshake completed136 ms
21 days agoHandshake completed90 ms
24 days agoHandshake completed84 ms
26 days agoHandshake completed85 ms
28 days agoCredentials required—

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

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 Final POS – Custom POS Builder and makes no claim about it beyond what these checks measured.