Remote MCP · Endpoint

com.okfindex/okfindex MCP server

No. com.okfindex/okfindex answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://okfindex.com/mcp

The last check completed an MCP handshake.

Registry name
com.okfindex/okfindex
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
365 ms
Tools exposed
107 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search Open Knowledge Format (OKF) bundles, read a bundle card and submit your own with IndexNow.
Listing
From the official MCP registry (active).
Recent checks of com.okfindex/okfindex
CheckedResultHandshake
7 hours agoHandshake completed365 ms
12 hours agoHandshake completed422 ms
2 days agoHandshake completed385 ms
4 days agoHandshake completed555 ms
7 days agoHandshake completed374 ms
9 days agoHandshake completed405 ms
11 days agoHandshake completed383 ms
14 days agoHandshake completed377 ms
15 days agoHandshake completed439 ms
18 days agoHandshake completed373 ms
20 days agoHandshake completed369 ms
21 days agoHandshake completed371 ms
23 days agoHandshake completed387 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.

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