Remote MCP · Endpoint

BuyWise MCP server

No. BuyWise answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://api.buywise.fyi/mcp

The last check completed an MCP handshake.

Registry name
fyi.buywise/buywise
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
202 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Know what you're buying: brand, white-label, price, fake-discount, review and seller checks
Website
https://buywise.fyi/
Listing
From the official MCP registry (active).
Recent checks of BuyWise
CheckedResultHandshake
5 hours agoHandshake completed202 ms
2 days agoHandshake completed143 ms
5 days agoHandshake completed128 ms
7 days agoHandshake completed67 ms
9 days agoHandshake completed103 ms
11 days agoHandshake completed117 ms
13 days agoHandshake completed76 ms
15 days agoHandshake completed81 ms
17 days agoHandshake completed71 ms
18 days agoHandshake completed100 ms
20 days agoHandshake completed138 ms
21 days agoHandshake completed762 ms
23 days agoHandshake completed236 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with BuyWise and makes no claim about it beyond what these checks measured.