# chat.avva/catalog (remote · avva.chat)

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

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `avva.chat`: 83/100 (this document), [markdown](https://verifymcp.io/servers/chat-avva-catalog/mcp-catalog.md), [page](https://verifymcp.io/servers/chat-avva-catalog/mcp-catalog)

## Channel facts

- Endpoint: `https://avva.chat/mcp-catalog`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 166 tokens (~83/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the chat.avva/catalog MCP server?

chat.avva/catalog is a hosted endpoint at https://avva.chat/mcp-catalog, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http chat-avva-catalog 'https://avva.chat/mcp-catalog'
```

### Cursor

```json
{
  "mcpServers": {
    "chat-avva-catalog": {
      "url": "https://avva.chat/mcp-catalog"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "chat-avva-catalog": {
      "type": "http",
      "url": "https://avva.chat/mcp-catalog"
    }
  }
}
```

### Codex

```toml
[mcp_servers.chat-avva-catalog]
url = "https://avva.chat/mcp-catalog"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chat-avva-catalog": {
      "type": "remote",
      "url": "https://avva.chat/mcp-catalog",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add chat-avva-catalog --url 'https://avva.chat/mcp-catalog' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  chat-avva-catalog:
    url: "https://avva.chat/mcp-catalog"
```

### Netclaw

```json
{
  "McpServers": {
    "chat-avva-catalog": {
      "Transport": "http",
      "Url": "https://avva.chat/mcp-catalog"
    }
  }
}
```

### Vellum

```bash
assistant mcp add chat-avva-catalog -t streamable-http -u 'https://avva.chat/mcp-catalog'
```

### Other

```json
{
  "mcpServers": {
    "chat-avva-catalog": {
      "type": "http",
      "url": "https://avva.chat/mcp-catalog"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 78, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [cosmetic] Tool “search” changed its title: Search the Avva expert catalog → Search the avva expert catalog

### 2026-09-10 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `search` (~43 tokens)

Search the avva expert catalog

Find published experts by domain, decision types, or wording. Returns result ids for fetch. Read-only.

Input parameters:

- `query` (string, required): What kind of judgment you are looking for.

Output parameters:

- `results` (array)

### `fetch` (~46 tokens)

Fetch one expert with their connector URL

Full catalog card for one expert by id (their slug), including the MCP connector URL your agent connects to consult them. Read-only.

Input parameters:

- `id` (string, required): An id returned by search.

Output parameters:

- `id` (string)
- `text` (string)
- `title` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/chat-avva-catalog/mcp-catalog#diagnostics

## Score history

- 2026-09-21: 83
- 2026-09-20: 82
- 2026-09-19: 82
- 2026-09-18: 81
- 2026-09-17: 81
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 78
- 2026-09-09: 77
- 2026-09-08: 77
- 2026-09-07: 76
- 2026-09-06: 76
- 2026-09-05: 76
- 2026-09-04: 75
- 2026-09-03: 75

## Common questions

### What is the chat.avva/catalog MCP server?

chat.avva/catalog is an MCP server listed in the public MCP registry as chat.avva/catalog. Search Avva for an expert, then connect their model - judgment from real past decisions. This page covers its hosted endpoint (https://avva.chat/mcp-catalog).

### Is the chat.avva/catalog MCP server safe to use?

chat.avva/catalog scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the chat.avva/catalog MCP server expose?

chat.avva/catalog exposes 2 tools: search, fetch. Their descriptions and schemas cost roughly 89 tokens of context every time the server is loaded.

### Does the chat.avva/catalog MCP server require authentication?

No. We connected to chat.avva/catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the chat.avva/catalog MCP server still maintained?

chat.avva/catalog is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://avva.chat/mcp-catalog
- Website: https://avva.chat/
- Changelog RSS feed: https://verifymcp.io/servers/chat-avva-catalog/mcp-catalog.xml
- Changelog JSON feed: https://verifymcp.io/servers/chat-avva-catalog/mcp-catalog.json
- HTML version of this page: https://verifymcp.io/servers/chat-avva-catalog/mcp-catalog