Remote MCP · Endpoint

io.github.Zyxel89/pretrade-oracle MCP server

Yes, as of 1 hour ago: the TLS certificate could not be verified.

DownLast checked 1 hour ago

Server URL

https://pretrade-oracle.duckdns.org/mcp

The last check failed: the TLS certificate could not be verified.

Registry name
io.github.Zyxel89/pretrade-oracle
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
1 tool
Uptime, last 30 days
31.6% from 19 checks
Described by its publisher as
Pre-trade oracle: real slippage, honeypot/sellability at size, exotic DEXs and new chains.
Listing
From the official MCP registry (active).
Recent checks of io.github.Zyxel89/pretrade-oracle
CheckedResultHandshake
1 hour agoFailed - the TLS certificate could not be verified—
1 day agoFailed - the TLS certificate could not be verified—
2 days agoFailed - the TLS certificate could not be verified—
3 days agoFailed - the TLS certificate could not be verified—
4 days agoFailed - the TLS certificate could not be verified—
5 days agoFailed - the TLS certificate could not be verified—
6 days agoFailed - the TLS certificate could not be verified—
8 days agoFailed - the TLS certificate could not be verified—
11 days agoFailed - the TLS certificate could not be verified—
13 days agoFailed - the TLS certificate could not be verified—
15 days agoFailed - the TLS certificate could not be verified—
18 days agoFailed - the TLS certificate could not be verified—
20 days agoFailed - the TLS certificate could not be verified—
22 days agoHandshake completed294 ms
24 days agoHandshake completed332 ms
26 days agoHandshake completed289 ms
27 days agoHandshake completed302 ms
28 days agoHandshake completed291 ms
29 days agoHandshake completed286 ms

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

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 io.github.Zyxel89/pretrade-oracle and makes no claim about it beyond what these checks measured.