Remote MCP · Endpoint

Regent Protocol MCP server

No. Regent Protocol answered an MCP handshake 52 minutes ago.

Up · key neededLast checked 52 minutes ago

Server URL

https://gw.regentprotocol.org/gw/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
org.regentprotocol/cloud-gateway
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
27 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Spending control for AI agents: approved budgets, a decision before each payment, signed receipts.
Listing
From the official MCP registry (active).
Recent checks of Regent Protocol
CheckedResultHandshake
52 minutes agoHandshake completed27 ms
3 days agoHandshake completed25 ms
12 days agoHandshake completed28 ms
13 days agoHandshake completed24 ms
14 days agoHandshake completed27 ms
15 days agoHandshake completed25 ms
17 days agoHandshake completed26 ms
18 days agoHandshake completed27 ms
18 days agoHandshake completed23 ms
20 days agoHandshake completed25 ms
22 days agoHandshake completed23 ms
25 days agoHandshake completed47 ms
27 days agoHandshake completed40 ms
29 days agoHandshake completed22 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 Regent Protocol and makes no claim about it beyond what these checks measured.