Avva Catalog MCP

A discovery-only MCP server that allows agents to search for and fetch details of expert Decision Models available on the Avva marketplace. It provides tools to browse expert profiles and retrieve their specific connector URLs, facilitating the connection to individual expert models for decision support.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by avva

MCP endpoint (Streamable HTTP)

https://avva.chat/mcp-catalog

Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 2 of 2 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 6, 2026, 1:42 PM UTC
Passed Official MCP Registry namespace is tied to avva.chat · Nov 6, 2026, 1:23 PM UTC
Passed Endpoint is on the registry namespace domain · Nov 6, 2026, 1:23 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Search for experts by domain or profile
Fetch expert profile details and connector URLs
Discover available Decision Models for agent consultation

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: chat.avva/catalog@1.0.0 Project website

Protocol and capabilities

Server: avva-catalog 1.0.0
MCP protocol negotiated in check: 2025-11-25
Tools: 2 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

The avva expert catalog: professionals publish their real past decisions as models your agent can consult before it answers. This server is discovery only — search the catalog, fetch one expert, then connect that expert’s own MCP URL (returned by fetch) to actually consult them. Coverage labels describe how much of an expert’s material their published cases and rules rest on, never predictive accuracy.

Tools

2 advertised

search — Search the avva expert catalog

Advertised by the server during the last successful anonymous check.

Advertised read-only

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

search input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 500,
      "minLength": 1,
      "description": "What kind of judgment you are looking for."
    }
  },
  "additionalProperties": false
}

search output schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "results"
  ],
  "properties": {
    "results": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id",
          "title",
          "url"
        ],
        "properties": {
          "id": {
            "type": "string"
          },
          "url": {
            "type": "string"
          },
          "title": {
            "type": "string"
          }
        },
        "additionalProperties": false
      }
    }
  },
  "additionalProperties": false
}

search annotations

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

fetch — Fetch one expert with their connector URL

Advertised by the server during the last successful anonymous check.

Advertised read-only

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

fetch input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1,
      "description": "An id returned by search."
    }
  },
  "additionalProperties": false
}

fetch output schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id",
    "title",
    "text",
    "url"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "url": {
      "type": "string"
    },
    "text": {
      "type": "string"
    },
    "title": {
      "type": "string"
    },
    "metadata": {
      "type": "object",
      "required": [
        "connector_url",
        "profile_url",
        "kind",
        "coverage"
      ],
      "properties": {
        "kind": {
          "enum": [
            "expert",
            "house"
          ],
          "type": "string"
        },
        "coverage": {
          "type": "string"
        },
        "profile_url": {
          "type": "string"
        },
        "connector_url": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}

fetch annotations

{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

2026-11-06: 1 of 1 checks answered
2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 1589 ms
95th percentile latency: 1589 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 6, 2026, 1:42 PM UTC · probe · passed · 1589 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add avva-catalog-mcp --url https://avva.chat/mcp-catalog

Cursor

Merge this server into .cursor/mcp.json in your project, then enable avva-catalog-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "avva-catalog-mcp": {
      "type": "streamableHttp",
      "url": "https://avva.chat/mcp-catalog",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start avva-catalog-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http avva-catalog-mcp https://avva.chat/mcp-catalog

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://avva.chat/mcp-catalog

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "avva-catalog-mcp": {
      "serverUrl": "https://avva.chat/mcp-catalog"
    }
  }
}

Let your agent find its tools

Find servers like Avva Catalog MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 5,216

Do you run Avva Catalog MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing