Remote MCP · Endpoint

holdmark · facts about online stores MCP server

No. holdmark · facts about online stores answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://holdmark.org/mcp

The last check completed an MCP handshake.

Registry name
org.holdmark/registry
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
315 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Does this store deliver and refund? Measured with carriers and payment processors.
Listing
From the official MCP registry (active).
Recent checks of holdmark · facts about online stores
CheckedResultHandshake
42 minutes agoHandshake completed315 ms
3 days agoHandshake completed278 ms
13 days agoHandshake completed284 ms
13 days agoHandshake completed274 ms
15 days agoHandshake completed322 ms
15 days agoHandshake completed442 ms
17 days agoHandshake completed274 ms
18 days agoHandshake completed278 ms
18 days agoHandshake completed288 ms
20 days agoHandshake completed301 ms
22 days agoHandshake completed360 ms
25 days agoHandshake completed272 ms
27 days agoHandshake completed292 ms

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 holdmark · facts about online stores and makes no claim about it beyond what these checks measured.