mcpbeat Sign in

Liminary MCP Server

by liminary-api Your server? Claim it
answering

Liminary is answering right now. Last checked 2 min ago.

Your AI's memory for what you actually know: recall across your documents, notes, and meetings

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

Nothing serious here today

Today is the operative word: we check Liminary every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 2 min ago.

run in your terminal
claude mcp add mcp --transport http https://api.liminary.io/api/mcp/
Settings → Connectors → Add custom connector, then paste this address
https://api.liminary.io/api/mcp/
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://api.liminary.io/api/mcp/"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.liminary.io/api/mcp/"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://api.liminary.io/api/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://api.liminary.io/api/mcp/ streamable-http sign-in 634 ms 2 min ago

Alternatives to Liminary

same job, measured the same way
Membase
by membase

Long-term memory for you and your AIs: search memories, read the profile, add facts and documents.

answering
A
Andish
by andish

Knowledge-graph memory for your team's documents. Answers cite the source, not a summary.

124 installs/wk local only
NoteCube
by notecube

Your NoteCube meeting and lecture recordings: search, read transcripts, and write cited documents.

answering
Mazarbul
by mo-cmyk

Local-first memory for AI agents: entities, facts, relations and documents with semantic recall.

local only
Ilu Rennik
by ilurennik

Personal memory for you and your AI. Your insurance, accounts, IDs, documents and people.

answering
ONRC trade register
by foreverworks

Follow your filings at Romania's trade register, with their documents, fee notes and invoices.

548 installs/wk local only
SuperLocalMemory
by qualixar

Local-first memory for AI agents: recall with sources, answer checks, documents, mesh, governance.

1 251 installs/wk local only
InterMIND
by intermind

Your InterMIND meetings, recaps, transcripts, channels and documents, from your assistant.

answering

Liminary — questions

Answers built from our own checks of this server.

Why is there no tool list for Liminary?
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 Liminary 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 650 ms. The bar chart above shows every period we have measured.
How do I connect Liminary?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form 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 Liminary?
No API key is involved. Liminary 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 Liminary?
It answers our handshake in 650 ms on average, which is faster than 15% 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.