Remote MCP · Endpoint

OneFindMe MCP server

No. OneFindMe answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://onefindme.com/mcp

The last check completed an MCP handshake.

Registry name
com.onefindme/search
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
127 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search AliExpress and eBay in any language: real listings with price, rating, delivery and links.
Listing
From the official MCP registry (active).
Recent checks of OneFindMe
CheckedResultHandshake
1 hour agoHandshake completed127 ms
2 days agoHandshake completed78 ms
5 days agoHandshake completed94 ms
7 days agoHandshake completed268 ms
9 days agoHandshake completed80 ms
11 days agoHandshake completed92 ms
13 days agoHandshake completed116 ms
15 days agoHandshake completed165 ms
17 days agoHandshake completed109 ms
18 days agoHandshake completed135 ms
20 days agoHandshake completed169 ms
21 days agoHandshake completed161 ms
23 days agoHandshake completed63 ms
25 days agoHandshake completed159 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 OneFindMe and makes no claim about it beyond what these checks measured.