Remote MCP · Endpoint

BuyRecord MCP server

No. BuyRecord answered an MCP handshake 15 minutes ago.

UpLast checked 15 minutes ago

Server URL

https://api.buyrecord.app/mcp

The last check completed an MCP handshake.

Registry name
app.buyrecord/buyrecord
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
307 ms
Tools exposed
5 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
US product return policies, recalls and, as stores join, verified purchase outcomes for AI agents.
Listing
From the official MCP registry (active).
Recent checks of BuyRecord
CheckedResultHandshake
15 minutes agoHandshake completed307 ms
9 days agoHandshake completed295 ms
9 days agoHandshake completed295 ms
11 days agoHandshake completed297 ms
12 days agoHandshake completed297 ms
13 days agoHandshake completed297 ms
14 days agoHandshake completed476 ms
14 days agoHandshake completed292 ms
16 days agoHandshake completed301 ms
19 days agoHandshake completed291 ms
21 days agoHandshake completed295 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed294 ms
28 days agoHandshake completed297 ms

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

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