Remote MCP · Endpoint

Reevol Source: supplier search MCP server

No. Reevol Source: supplier search answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://source.reevol.com/mcp

The last check completed an MCP handshake.

Registry name
com.reevol.source/supplier-search
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
32 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search and compare 200,000+ global suppliers by brief, name, HS code or country. Free, no key.
Listing
From the official MCP registry (active).
Recent checks of Reevol Source: supplier search
CheckedResultHandshake
1 hour agoHandshake completed32 ms
1 day agoHandshake completed114 ms
2 days agoHandshake completed72 ms
3 days agoHandshake completed40 ms
4 days agoHandshake completed62 ms
5 days agoHandshake completed31 ms
6 days agoHandshake completed198 ms
9 days agoHandshake completed50 ms
11 days agoHandshake completed33 ms
14 days agoHandshake completed34 ms
16 days agoHandshake completed359 ms
18 days agoHandshake completed38 ms
20 days agoHandshake completed97 ms
22 days agoHandshake completed27 ms

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

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 Reevol Source: supplier search and makes no claim about it beyond what these checks measured.