Remote MCP · Endpoint

Paddock Cards MCP server

No. Paddock Cards answered an MCP handshake 3 days ago.

UpLast checked 3 days ago

Server URL

https://api.paddock.so/agent-commerce/mcp

The last check completed an MCP handshake.

Registry name
so.paddock/cards
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
35 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
Send birthday cards, Christmas cards and postcards, printed and mailed for you.
Listing
From the official MCP registry (active).
Recent checks of Paddock Cards
CheckedResultHandshake
3 days agoHandshake completed35 ms
7 days agoHandshake completed30 ms
16 days agoHandshake completed23 ms
17 days agoHandshake completed26 ms
19 days agoHandshake completed22 ms
19 days agoHandshake completed20 ms
21 days agoHandshake completed62 ms
22 days agoHandshake completed27 ms
22 days agoHandshake completed37 ms
24 days agoHandshake completed22 ms
26 days agoHandshake completed37 ms

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

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