Remote MCP · Endpoint

Subpay Document Reader MCP server

No. Subpay Document Reader answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://subpay.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.subpay/document-reader
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
155 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Reads AIA G702/G703 pay applications and change orders from PDF to JSON. $0.04/page via x402.
Listing
From the official MCP registry (active).
Recent checks of Subpay Document Reader
CheckedResultHandshake
1 hour agoHandshake completed155 ms
2 days agoHandshake completed156 ms
4 days agoHandshake completed86 ms
7 days agoHandshake completed113 ms
9 days agoHandshake completed115 ms
11 days agoHandshake completed123 ms
13 days agoHandshake completed163 ms
15 days agoHandshake completed95 ms
17 days agoHandshake completed222 ms
19 days agoHandshake completed106 ms
20 days agoHandshake completed103 ms
22 days agoHandshake completed145 ms
23 days agoHandshake completed1.24 s

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

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