Remote MCP · Endpoint

PayeeProof MCP server

No. PayeeProof answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://payeeproof.davisvillelabs.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.davisvillelabs/payeeproof
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
407 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Payment identity intelligence for AI agents.
Listing
From the official MCP registry (active).
Recent checks of PayeeProof
CheckedResultHandshake
1 day agoHandshake completed407 ms
3 days agoHandshake completed650 ms
5 days agoHandshake completed189 ms
8 days agoHandshake completed199 ms
9 days agoHandshake completed333 ms
11 days agoHandshake completed245 ms
12 days agoHandshake completed338 ms
13 days agoHandshake completed374 ms
15 days agoHandshake completed149 ms
17 days agoHandshake completed211 ms
19 days agoHandshake completed299 ms
20 days agoHandshake completed319 ms
22 days agoHandshake completed280 ms
23 days agoHandshake completed144 ms

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