Remote MCP · Endpoint

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

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

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

The last check failed: the server returned an HTTP error.

Registry name
io.github.nexus-mcp-infra/similarity-search-api-sdk
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
61.1% from 18 checks
Described by its publisher as
Stateless NMI + cosine fusion with entropy-driven alpha calibration
Repository
https://github.com/nexus-mcp-infra/similarity-search-api-sdk
Listing
From the official MCP registry (active).
Recent checks of io.github.nexus-mcp-infra/similarity-search-api-sdk
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
9 days agoHandshake completed627 ms
11 days agoHandshake completed1.06 s
14 days agoHandshake completed1.17 s
16 days agoHandshake completed3.20 s
18 days agoHandshake completed1.31 s
20 days agoHandshake completed936 ms
22 days agoHandshake completed1.15 s
24 days agoHandshake completed898 ms
26 days agoHandshake completed358 ms
28 days agoHandshake completed987 ms
29 days agoHandshake completed324 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 22 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.nexus-mcp-infra/similarity-search-api-sdk and makes no claim about it beyond what these checks measured.