Remote MCP · Endpoint

Paylyte MCP server

No. Paylyte answered an MCP handshake 32 minutes ago.

UpLast checked 32 minutes ago

Server URL

https://api.paylyte.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.paylyte/paylyte-core
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
100 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Agent Trust Score earned through Proof of Outcome. Browse and buy as paylyte-core.
Listing
From the official MCP registry (active).
Recent checks of Paylyte
CheckedResultHandshake
32 minutes agoHandshake completed100 ms
3 days agoHandshake completed100 ms
13 days agoHandshake completed80 ms
13 days agoHandshake completed106 ms
15 days agoHandshake completed87 ms
16 days agoHandshake completed134 ms
17 days agoHandshake completed83 ms
18 days agoHandshake completed123 ms
18 days agoHandshake completed77 ms
20 days agoHandshake completed417 ms
22 days agoHandshake completed91 ms
25 days agoHandshake completed116 ms
27 days agoHandshake completed109 ms
29 days agoHandshake completed479 ms

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

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