Remote MCP · Endpoint

run.pay MCP server

No. run.pay answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://runpay-backend-visibility-production.up.railway.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.PalabreX/runpay
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
259 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Stripe-native marketplace where AI agents discover and pay per call for API services.
Website
https://getrunpay.com/
Repository
https://github.com/PalabreX/runpay-mcp
Listing
From the official MCP registry (active).
Recent checks of run.pay
CheckedResultHandshake
2 hours agoHandshake completed259 ms
2 days agoHandshake completed267 ms
4 days agoHandshake completed267 ms
5 days agoHandshake completed254 ms
7 days agoHandshake completed259 ms
8 days agoHandshake completed262 ms
9 days agoHandshake completed258 ms
12 days agoHandshake completed259 ms
13 days agoHandshake completed301 ms
15 days agoHandshake completed281 ms
17 days agoHandshake completed255 ms
18 days agoHandshake completed249 ms
19 days agoHandshake completed259 ms
20 days agoHandshake completed260 ms
20 days agoHandshake completed244 ms
21 days agoHandshake completed265 ms
23 days agoHandshake completed259 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with run.pay and makes no claim about it beyond what these checks measured.