NASC — Networked AI Session Continuity MCP Server

by archerionlabs Your server? Claim it

answering

NASC — Networked AI Session Continuity is answering right now. Last checked 6 min ago.

Shared memory across AI dev tools: each session hands its context to the next, not starting cold.

Uptime history 47 days of history · worst day 99%

47 days agonow

98.9%

Uptime 24h

91 of 92 checks

—

Tools

hidden behind auth

625 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

NASC — Networked AI Session Continuity missed 2 checks 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 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add nasc --transport http https://nasc.archerionlabs.com/mcp

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

{
  "mcpServers": {
    "nasc": {
      "url": "https://nasc.archerionlabs.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.nasc]
url = "https://nasc.archerionlabs.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "nasc": {
      "url": "https://nasc.archerionlabs.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "nasc": {
      "url": "https://nasc.archerionlabs.com/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://nasc.archerionlabs.com/mcp	streamable-http	sign-in	436 ms	6 min ago

Alternatives to NASC — Networked AI Session Continuity

same job, measured the same way

Agendum

by sralli

AI agent memory: task tracking, scoped work packages, decisions, and cross-session continuity

102 installs/wk local only

Mindswap

by shiporbleed

Local-first AI context and memory server for cross-tool coding continuity.

45 installs/wk local only

Codeledger

by codeledgerecf

Deterministic context selection for AI coding agents. Local memory that compounds across sessions.

435 installs/wk local only

Deerdawn

by deerdawn

AI session memory: the brief your AI reads before every session so no session starts cold.

413 installs/wk 24 tools answering

OneAIMemory

by amxncode

Cross-device AI memory with encrypted activity capture and context handoff between AI tools

answering

Epiphany

by gatsv-tech

One private, local memory your AI tools share. Cross-model, on-device, never lose a session.

40 installs/wk local only

Mindmap MCP Server

by ravi-labs

Local-first memory & context-handoff across AI tools — capture in one, resume in another. No cloud.

39 installs/wk local only

XMemo

by yonro

Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.

274 installs/wk answering

NASC — Networked AI Session Continuity — questions

Answers built from our own checks of this server.

Why is there no tool list for NASC — Networked AI Session Continuity?

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: 98.9% of checks in the last 24 hours got a reply.

Is NASC — Networked AI Session Continuity working right now?

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

How do I connect NASC — Networked AI Session Continuity?

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 NASC — Networked AI Session Continuity?

No API key is involved. NASC — Networked AI Session Continuity 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 NASC — Networked AI Session Continuity?

It answers our handshake in 625 ms on average, which is faster than 20% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.