# A2UI Atomic Catalog docs (remote · a2uicatalog.ai)

Search the A2UI Atomic Catalog's own docs: auth, versioning, pricing, API surface.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `a2uicatalog.ai`: 71/100 (this document), [markdown](https://verifymcp.io/servers/ai-a2uicatalog-docs/mcp-docs.md), [page](https://verifymcp.io/servers/ai-a2uicatalog-docs/mcp-docs)

## Channel facts

- Endpoint: `https://a2uicatalog.ai/mcp-docs`
- 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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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 266 tokens (~133/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the A2UI Atomic Catalog docs MCP server?

A2UI Atomic Catalog docs is a hosted endpoint at https://a2uicatalog.ai/mcp-docs, 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 ai-a2uicatalog-docs 'https://a2uicatalog.ai/mcp-docs'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-a2uicatalog-docs": {
      "url": "https://a2uicatalog.ai/mcp-docs"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-a2uicatalog-docs": {
      "type": "http",
      "url": "https://a2uicatalog.ai/mcp-docs"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-a2uicatalog-docs]
url = "https://a2uicatalog.ai/mcp-docs"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-a2uicatalog-docs --url 'https://a2uicatalog.ai/mcp-docs' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-a2uicatalog-docs:
    url: "https://a2uicatalog.ai/mcp-docs"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-a2uicatalog-docs": {
      "Transport": "http",
      "Url": "https://a2uicatalog.ai/mcp-docs"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-a2uicatalog-docs -t streamable-http -u 'https://a2uicatalog.ai/mcp-docs'
```

### Other

```json
{
  "mcpServers": {
    "ai-a2uicatalog-docs": {
      "type": "http",
      "url": "https://a2uicatalog.ai/mcp-docs"
    }
  }
}
```

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-11-21 (score 71, +1)

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

### 2026-11-18 (score 70, +1)

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

### 2026-11-16 (score 69, +1)

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

### 2026-11-14 (score 68, +1)

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

### 2026-11-12 (score 67, +1)

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

### 2026-11-11 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-10 (score 66)

First indexed and scored.

## MCP tools (2)

### `search_docs` (~105 tokens)

Use this to answer a question about the product (auth, versioning, pricing, API surface, runbook catalog) from its own documentation, given a plain-English query. Returns {results}: ranked sections, each with title, section, a text snippet, a score and the real source URL, never fabricated content; empty if nothing matches.

Input parameters:

- `max_results` (integer): Max results to return. Default 5.
- `query` (string, required): Plain-English question or keywords.

Output parameters:

- `note` (string): Set when nothing matched.
- `results` (array): Ranked sections, best first.

### `list_docs` (~68 tokens)

Use this to browse everything the documentation index holds when you have no specific query, or to see what topics exist before searching. Returns the indexed sections as entries of title, section and url, up to max_results.

Input parameters:

- `max_results` (integer): Max entries to return. Omit for all.

Output parameters:

- `docs` (array): Indexed sections.
- `total` (integer): Total sections in the index.

## Diagnostics

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

## Score history

- 2026-11-21: 71
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 68
- 2026-11-14: 68
- 2026-11-13: 67
- 2026-11-12: 67
- 2026-11-11: 66
- 2026-11-10: 66

## Common questions

### What is the A2UI Atomic Catalog docs MCP server?

A2UI Atomic Catalog docs is an MCP server listed in the public MCP registry as ai.a2uicatalog/docs. Search the A2UI Atomic Catalog's own docs: auth, versioning, pricing, API surface. This page covers its hosted endpoint (https://a2uicatalog.ai/mcp-docs).

### Is the A2UI Atomic Catalog docs MCP server safe to use?

A2UI Atomic Catalog docs scores 71 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 A2UI Atomic Catalog docs MCP server expose?

A2UI Atomic Catalog docs exposes 2 tools: search_docs, list_docs. Their descriptions and schemas cost roughly 173 tokens of context every time the server is loaded.

### Does the A2UI Atomic Catalog docs MCP server require authentication?

No. We connected to A2UI Atomic Catalog docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the A2UI Atomic Catalog docs MCP server still maintained?

A2UI Atomic Catalog docs is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the A2UI Atomic Catalog docs MCP server?

VerifyMCP ran 13 checks on A2UI Atomic Catalog docs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://a2uicatalog.ai/mcp-docs
- Repository: https://github.com/a2uicatalog/a2ui
- Website: https://a2uicatalog.ai/docs/
- Changelog RSS feed: https://verifymcp.io/servers/ai-a2uicatalog-docs/mcp-docs.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-a2uicatalog-docs/mcp-docs/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-a2uicatalog-docs/mcp-docs.json
- HTML version of this page: https://verifymcp.io/servers/ai-a2uicatalog-docs/mcp-docs
