mcpbeat Sign in

chat-recall MCP Server

answering

chat-recall is answering right now. Last checked 14 min ago. 261 installs a week from npm. Last commit 14 Oct 2026.

One searchable history across every AI coding tool, with secret scanning and a shared task board.

Installs per day peak 914 · avg 189 · +62% w/w
a month agotoday
Uptime history 53 days of history · worst day 95%
53 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
214 ms
Response time
average over 24h
261
Installs / week
npm and PyPI

What the code does

We read the source, 2 d ago · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Sends data to a third-party sink packages/server/src/services/builtin-rulepack.ts:140
  { name: 'slack-webhook-url', regex: '(?:https?://)?hooks.slack.com/(?:services|workflows|triggers)/[A-Za-z0-9+/]{43,56}', severity: 'medium' },
Reads files and sends them to the network packages/cli/src/sync-client.ts:36
import { readFileSync, writeFileSync, mkdirSync, mkdtempSync, rmSync, chmodSync, unlinkSync, readdirSync, statSync } from 'node:fs';
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

Touches key and credential files .github/ISSUE_TEMPLATE/bug_report.yml:12
        **Do not paste secrets.** Session transcripts and `.npmrc`/`.env` files

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

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 chat-recall --transport http https://chatrecall.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "chat-recall": {
      "url": "https://chatrecall.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.chat-recall]
url = "https://chatrecall.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "chat-recall": {
      "url": "https://chatrecall.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "chat-recall": {
      "url": "https://chatrecall.dev/mcp"
    }
  }
}

This one needs environment variables set before it will start: CHAT_RECALL_SERVER (Server to sync to. Defaults to the hosted service at https://chatrecall.dev; set it to your own instance to self-host. Self-hosting is free for one person.), CHAT_RECALL_MCP_PROFILE (Which tools to register: "lean" (default, 28 tools — tool choice degrades as the list grows) or "full" (all 63 tools, plus recall_help — a directory of the rest; 4 code-intelligence tools register only with the codeindex companion on PATH). Every tool works when called by name either way.), CHAT_RECALL_NO_DAEMON (Set to 1 to load the whole server inside each session. By default every session with the same profile and server shares one background daemon, and each session is a thin relay onto it — the engine is loaded once per machine instead of once per session. Turn it off for a sandbox with no writable runtime directory.), CHAT_RECALL_DAEMON_IDLE_SECS (Seconds with no session attached before the shared daemon exits and returns its memory. Default 900. Set 0 to keep it resident.). The author declared them in the registry entry; get the values from the project itself.

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://chatrecall.dev/mcp streamable-http sign-in 237 ms 14 min ago

Alternatives to chat-recall

same job, measured the same way
Ghosthunt
by 78degrees

Find every leaked secret on your machine — API keys in .env files, shell history, and configs.

34 installs/wk local only
Arcwall Security
by rom-baro

Security scanning for AI coding tools. Detects secrets, threat models, and runs pre-commit checks.

29 installs/wk local only
mcpcut
by rostislavmatov

Journals every MCP tool call with secrets redacted; with a policy, holds risky calls for approval

592 installs/wk local only
Keystash
by thu-lawyer

Keychain-backed secret broker: an AI agent can use your keys, but no tool ever returns one.

519 installs/wk local only
Jeikin
by jeikin

Accessibility compliance for AI coding tools. WCAG 2.2 reviews with shared evidence.

answering
Bridgeguard MCP
by kota1026

BridgeGuard MCP Server - Cross-chain bridge security audit tools for AI coding agents. Scan bri...

33 installs/wk local only
Keyspoor
by majiayu000

Offline secret scanning for AI agents. Redacted findings; scans text and files in a chosen root.

245 installs/wk local only
LeakRank Guard
by prototeemo

Scans code changes for leaked secrets and insecure config, with actionable fixes for AI agents.

39 installs/wk local only

chat-recall — questions

Answers built from our own checks of this server.

Why is there no tool list for chat-recall?
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 chat-recall 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 214 ms. The bar chart above shows every period we have measured.
How do I connect chat-recall?
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 chat-recall?
No API key is involved. chat-recall 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 chat-recall?
It answers our handshake in 214 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use chat-recall?
The npm package chat-recall was installed 261 times in the last week. Week over week that is +62%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is chat-recall open source?
No, and the distinction matters: its licence is declared as Elastic-2.0. That makes it source-available — you can read the code, but the terms are the author's own, not one of the recognised open-source licences. Read them before you build on it.