Remote MCP · Endpoint

Thrifle MCP server

No. Thrifle answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.thrifle.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.thrifle/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
375 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
US return policies, price-match rules, discounts, deals and Amazon price verdicts. Read-only.
Listing
From the official MCP registry (active).
Recent checks of Thrifle
CheckedResultHandshake
1 hour agoHandshake completed375 ms
2 days agoHandshake completed302 ms
4 days agoHandshake completed320 ms
5 days agoHandshake completed330 ms
7 days agoHandshake completed244 ms
8 days agoHandshake completed2.42 s
9 days agoHandshake completed271 ms
12 days agoHandshake completed239 ms
13 days agoHandshake completed316 ms
15 days agoHandshake completed281 ms
16 days agoHandshake completed325 ms
17 days agoHandshake completed277 ms
19 days agoHandshake completed249 ms
20 days agoHandshake completed252 ms
20 days agoHandshake completed269 ms
21 days agoHandshake completed270 ms
22 days agoHandshake completed1.27 s

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

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