Remote MCP · Endpoint

FrankoX MCP server

No. FrankoX answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://frankox.com/mcp

The last check completed an MCP handshake.

Registry name
com.frankox/trade-intelligence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
330 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Verified opt-in trade profiles and consented manufacturer drafts; no private customer data.
Listing
From the official MCP registry (active).
Recent checks of FrankoX
CheckedResultHandshake
7 hours agoHandshake completed330 ms
4 days agoHandshake completed307 ms
14 days agoHandshake completed326 ms
15 days agoHandshake completed307 ms
15 days agoHandshake completed304 ms
17 days agoHandshake completed353 ms
18 days agoHandshake completed317 ms
19 days agoHandshake completed317 ms
20 days agoHandshake completed306 ms
21 days agoHandshake completed307 ms
23 days agoHandshake completed304 ms
26 days agoHandshake completed298 ms

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

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