mcpbeat

Agentic Diaries Audit MCP Server

io.github.kandikandikandi/behavioral-audit
not responding

Agentic Diaries Audit is listed as active in the registry but did not answer our last check. It exposes 1 tools. Last commit 19 Jul 2026.

Checks what a support agent knew but did not say against its policies. Free tier, no login.

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
2.2%
Uptime 24h
2 of 91 checks
1
Tools
read from the server
1215 ms
Response time
average over 24h
0
Stars
last commit 19 Jul 2026

Connect this server

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

run in your terminal
claude mcp add behavioral-audit --transport http https://receipts-mcp.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "behavioral-audit": {
      "url": "https://receipts-mcp.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.behavioral-audit]
url = "https://receipts-mcp.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "behavioral-audit": {
      "url": "https://receipts-mcp.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "behavioral-audit": {
      "url": "https://receipts-mcp.vercel.app/api/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

disclosure
disclosure_check
Check a draft support reply for disclosure gaps before sending it. Given what the customer said and the reply you are about to send, it flags any should-know policy the customer's situation made relevant that the draft failed to proactively surface (the knew-but-did-not-say gap). Returns a verdict (pass or gap); on a gap, each missed policy and the line that should have been surfaced. It detects and suggests, it does not rewrite.

Endpoints

URLTransportStateLatencyChecked
https://receipts-mcp.vercel.app/api/mcp streamable-http answering 44 ms 6 min ago

Agentic Diaries Audit — questions

Answers built from our own checks of this server.

What can Agentic Diaries Audit do?
It exposes 1 tools, read directly from the server on our last check. Among them: disclosure_check. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Agentic Diaries Audit working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 2 of 91 checks got a reply (2.2%), average response time 1215 ms. The bar chart above shows every period we have measured.
The registry lists Agentic Diaries Audit as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Agentic Diaries Audit?
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.
Does Agentic Diaries Audit need an API key?
No. Agentic Diaries Audit completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agentic Diaries Audit?
It answers our handshake in 1215 ms on average, which is faster than 3% 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.
Is Agentic Diaries Audit open source?
Yes — written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.