Nexsus MCP Server

by dbnexsus Your server? Claim it

answering

Nexsus is answering right now. Last checked 3 min ago.

Private persistent memory for Claude, ChatGPT & Gemini via MCP - semantic search, zero-code setup.

Uptime history 47 days of history · worst day 99%

47 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

473 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nexsus missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add nexsus --transport http https://app.nexsus.com.au/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "nexsus": {
      "url": "https://app.nexsus.com.au/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.nexsus]
url = "https://app.nexsus.com.au/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "nexsus": {
      "url": "https://app.nexsus.com.au/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "nexsus": {
      "url": "https://app.nexsus.com.au/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://app.nexsus.com.au/mcp	streamable-http	sign-in	410 ms	3 min ago

Alternatives to Nexsus

same job, measured the same way

Longmem

by marerem

Persistent cross-project memory for Cursor and Claude Code using local semantic search.

49 installs/wk local only

Claudex

by kunwar-shah

Persistent memory + FTS5 search MCP server for Claude Code conversation history.

84 installs/wk local only

Melchizedek

by louis49

Persistent memory for Claude Code — offline, single-file, hybrid search.

42 installs/wk local only

LLMemory

by meir-may

Search your AI chat history (ChatGPT, Claude, Codex) from any MCP client. Remote, private, read-only

answering

Contextforge MCP

by alfredoizdev

Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot.

197 installs/wk local only

Vectr

by swapnanil

Semantic codebase search + persistent working memory for AI code editors. Local, no API key.

541 installs/wk local only

Recall

by clauderecallhq

Persistent memory for Claude Code. Search, recall, and re-inject context from any session.

430 installs/wk local only

Recall

by clauderecall

Persistent memory for Claude Code. Search, recall, and re-inject context from any session.

local only

Nexsus — questions

Answers built from our own checks of this server.

Why is there no tool list for Nexsus?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Nexsus working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 473 ms. The bar chart above shows every period we have measured.

How do I connect Nexsus?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Nexsus?

No API key is involved. Nexsus answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Nexsus?

It answers our handshake in 473 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.