mcpbeat Sign in

LogRack MCP Server

answering

LogRack is answering right now. Last checked 14 min ago.

Shared memory for your AI tools: tasks, notes and context every tool can read and write over MCP.

Uptime history 47 hours of history
47 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
247 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check LogRack 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 14 min ago.

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

Alternatives to LogRack

same job, measured the same way
Basethread
by basethread

One shared context your team's AI tools read & write over MCP. No re-explaining. Free.

answering
Reef
by reefwith

Shared, living memory for you and your people — coves your AI assistant can read and write.

answering
Agentage Memory
by agentage

One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.

answering
NoteMCP
by notemcp

Save notes in seconds. Your AI can then search, read, write and tag them over MCP.

answering
Penlog
by penlog

Handwritten iPad journal your AI can read and write tasks back to, over MCP.

answering
Sensefold
by sensefold

Personal context for every AI: search, read, and write back to your private Markdown library.

answering
memsprout
by memsprout

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

answering
ContextStream MCP Server
by contextstreamio

ContextStream MCP server for code context, memory, search, and AI tools.

913 installs/wk local only

LogRack — questions

Answers built from our own checks of this server.

Why is there no tool list for LogRack?
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 LogRack working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 247 ms. The bar chart above shows every period we have measured.
How do I connect LogRack?
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 LogRack?
No API key is involved. LogRack 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 LogRack?
It answers our handshake in 247 ms on average, which is faster than 67% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.