Remote MCP · Endpoint

io.github.nexus-mcp-infra/similarity-search-api-sdk MCP server

No. io.github.nexus-mcp-infra/similarity-search-api-sdk answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://similarity-search-api-production.up.railway.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.nexus-mcp-infra/similarity-search-api-sdk
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
936 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Stateless NMI + cosine fusion with entropy-driven alpha calibration
Listing
From the official MCP registry (active).
Recent checks of io.github.nexus-mcp-infra/similarity-search-api-sdk
CheckedResultHandshake
2 hours agoHandshake completed936 ms
2 days agoHandshake completed1.15 s
4 days agoHandshake completed898 ms
5 days agoHandshake completed358 ms
7 days agoHandshake completed987 ms
8 days agoHandshake completed324 ms
9 days agoHandshake completed911 ms
12 days agoHandshake completed886 ms
13 days agoHandshake completed323 ms
15 days agoHandshake completed675 ms
17 days agoHandshake completed846 ms
18 days agoHandshake completed660 ms
19 days agoHandshake completed666 ms
20 days agoHandshake completed350 ms
20 days agoHandshake completed426 ms
21 days agoHandshake completed721 ms
23 days agoHandshake completed727 ms

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

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 io.github.nexus-mcp-infra/similarity-search-api-sdk and makes no claim about it beyond what these checks measured.