mcpbeat

NASC — Networked AI Session Continuity MCP Server

com.archerionlabs/nasc
answering

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

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

Uptime history 41 hours of history · worst hour 75%
41 hours agonow
98.9%
Uptime 24h
90 of 91 checks
—
Tools
hidden behind auth
662 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

Connect this server

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

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, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://nasc.archerionlabs.com/mcp streamable-http needs key 857 ms 11 min ago

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 90 of 91 checks got a reply (98.9%), average response time 662 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 will need your own key or an OAuth login: it refuses anonymous clients.
Does NASC — Networked AI Session Continuity need an API key?
Yes. Every time we knock, NASC — Networked AI Session Continuity answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is NASC — Networked AI Session Continuity?
It answers our handshake in 662 ms on average, which is faster than 14% 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.