Remote MCP · Endpoint

Paddock MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://paddock.finance/api/mcp/mcp

The last check failed: the server returned an HTTP error.

Registry name
finance.paddock/paddock
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
13 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
Pre-payment verification for AI agents.
Listing
From the official MCP registry (active).
Recent checks of Paddock
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
13 days agoHandshake completed228 ms
14 days agoHandshake completed231 ms
15 days agoHandshake completed127 ms
16 days agoHandshake completed86 ms
18 days agoHandshake completed99 ms
18 days agoHandshake completed120 ms
19 days agoHandshake completed140 ms
21 days agoHandshake completed193 ms
22 days agoHandshake completed239 ms
25 days agoHandshake completed96 ms
27 days agoHandshake completed113 ms
30 days agoHandshake completed132 ms

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

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