Remote MCP · Endpoint

UseTested — Receipts-Verified Service Reviews MCP server

No. UseTested — Receipts-Verified Service Reviews answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://usetested.com/mcp

The last check completed an MCP handshake.

Registry name
com.usetested/reviews
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
838 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Receipts-verified reviews of x402 services and paid APIs, before your agent pays.
Listing
From the official MCP registry (active).
Recent checks of UseTested — Receipts-Verified Service Reviews
CheckedResultHandshake
5 hours agoHandshake completed838 ms
3 days agoHandshake completed335 ms
12 days agoHandshake completed262 ms
12 days agoHandshake completed311 ms
14 days agoHandshake completed268 ms
15 days agoHandshake completed506 ms
16 days agoHandshake completed511 ms
17 days agoHandshake completed266 ms
18 days agoHandshake completed89 ms
19 days agoHandshake completed292 ms
22 days agoHandshake completed369 ms
25 days agoHandshake completed81 ms
27 days agoHandshake completed228 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 UseTested — Receipts-Verified Service Reviews and makes no claim about it beyond what these checks measured.