mcpbeat Sign in

Catalog MCP Server

answering

Catalog is answering right now. Last checked 8 min ago. It exposes 2 tools.

Search Avva for an expert, then connect their model - judgment from real past decisions.

Uptime history 61 days of history · worst day 80%
61 days agonow
96.7%
Uptime 24h
88 of 91 checks
2
Tools
read from the server
1043 ms
Response time
average over 24h
open, no key
Access
streamable-http

Catalog does not always answer

Over the last week it answered 96.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not 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 8 min ago.

run in your terminal
claude mcp add catalog --transport http https://avva.chat/mcp-catalog
Settings → Connectors → Add custom connector, then paste this address
https://avva.chat/mcp-catalog
~/.codex/config.toml
[mcp_servers.catalog]
url = "https://avva.chat/mcp-catalog"
.cursor/mcp.json
{
  "mcpServers": {
    "catalog": {
      "url": "https://avva.chat/mcp-catalog"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "catalog": {
      "type": "http",
      "url": "https://avva.chat/mcp-catalog"
    }
  }
}

Available tools 2

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

fetch
fetch
Full catalog card for one expert by id (their slug), including the MCP connector URL your agent connects to consult them. Read-only.
search
search
Find published experts by domain, decision types, or wording. Returns result ids for fetch. Read-only.

Endpoints

URLTransportStateLatencyChecked
https://avva.chat/mcp-catalog streamable-http answering 1025 ms 8 min ago

Alternatives to Catalog

same job, measured the same way
Memnest
by blue-b

Local memory for coding AIs: search past conversations and decisions from the original text.

local only
UK Case Law MCP Server from MCPBundles
by mcpbundles

Search UK court judgments and tribunal decisions from the National Archives

answering
Fr Judilibre
by pipeworx-io

French court decisions (Cour de cassation and the judicial courts under it) — search, read a…

453 installs/wk 47 tools answering
ContextStream MCP Server
by contextstream

The context platform for AI agents: code search, team decisions, and grounded project context.

answering
Recall
by clauderecall

Persistent memory for Claude Code and Codex. Search and re-inject context from any session.

local only
Laya Typed Decisions
by perrylink

Typed noul / choice / score judgments from a local Laya model, with token-budget preflight.

123 installs/wk local only
Ratevert MCP
by ratevert

Read-only Ratevert MCP for asset search, pair rates, and conversions.

4 tools answering
Perspect
by tryperspect

Convene a panel of expert AI personas to debate any decision from every side.

2 tools answering

Catalog — questions

Answers built from our own checks of this server.

What can Catalog do?
It exposes 2 tools, read directly from the server on our last check. Among them: fetch, search. 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 Catalog working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 88 of 91 checks got a reply (96.7%), average response time 1043 ms. The bar chart above shows every period we have measured.
How do I connect Catalog?
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.
Does Catalog need an API key?
No. Catalog completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Catalog?
It answers our handshake in 1043 ms on average, which is faster than 6% 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.