mcpbeat Sign in

Nysa MCP Server

answering

Nysa is answering right now. Last checked 1 min ago.

Shared memory for teams that work with AI agents: meetings, email and calendar in one brain.

Uptime history 10 days of history · worst day 97%
10 days agonow
98.9%
Uptime 24h
91 of 92 checks
—
Tools
hidden behind auth
375 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nysa 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.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add nysa --transport http https://mcp.usenysa.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "nysa": {
      "url": "https://mcp.usenysa.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.nysa]
url = "https://mcp.usenysa.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "nysa": {
      "url": "https://mcp.usenysa.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "nysa": {
      "url": "https://mcp.usenysa.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

URLTransportStateLatencyChecked
https://mcp.usenysa.com/mcp streamable-http sign-in 372 ms 1 min ago

Alternatives to Nysa

same job, measured the same way
Korpus
by korpus

Shared memory for teams and their AI agents: Markdown concepts with typed links in shared bundles.

answering
Evc Mesh MCP
by entire-vc

Tasks, comments, shared memory and handoffs for teams of people and AI agents, over MCP.

answering
Bilg
by bilgai

Shared memory for coding agents and their teams: docs, epics, tasks and decisions over MCP.

answering
OneLore
by onelore

Shared project context for AI agents and teams: docs, tasks, and messages that stay current.

answering
Google Workspace (gsuite-sdk)
by pabloalaniz

Gmail, Calendar, Drive, Sheets, Tasks and Contacts for agents, with your own Google login

1 417 installs/wk local only
Local MCP
by lanchuske

Native macOS MCP server — 82 tools for Mail, Calendar, Teams, OneDrive and more.

local only
memsprout
by memsprout

shared AI-context layer for teams — persistent memory your agents search and update over MCP

answering
MailFlat
by mailflat

Real email inboxes for AI agents: open an address, read the one-time code, send mail.

380 installs/wk local only

Nysa — questions

Answers built from our own checks of this server.

Why is there no tool list for Nysa?
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 Nysa 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 375 ms. The bar chart above shows every period we have measured.
How do I connect Nysa?
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 Nysa?
No API key is involved. Nysa 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 Nysa?
It answers our handshake in 375 ms on average, which is faster than 34% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.