# ai.kaiv/docker-facts (remote · api.kaiv.ai)

Does that Docker tag actually exist? Real tags, sizes and platforms, live from Docker Hub.

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

## Components

- remote · `api.kaiv.ai`: 82/100 (this document), [markdown](https://verifymcp.io/servers/ai-kaiv-docker-facts/api-bridge-mcp-docker-facts-adc41b39.md), [page](https://verifymcp.io/servers/ai-kaiv-docker-facts/api-bridge-mcp-docker-facts-adc41b39)

## Channel facts

- Endpoint: `https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39`
- 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-20.

- **Endpoint Security**: 83/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 is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 467 tokens (~155/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ai.kaiv/docker-facts MCP server?

ai.kaiv/docker-facts is a hosted endpoint at https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39, 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-kaiv-docker-facts 'https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-kaiv-docker-facts": {
      "url": "https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-kaiv-docker-facts": {
      "type": "http",
      "url": "https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-kaiv-docker-facts]
url = "https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-kaiv-docker-facts": {
      "type": "remote",
      "url": "https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-kaiv-docker-facts --url 'https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-kaiv-docker-facts:
    url: "https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-kaiv-docker-facts": {
      "Transport": "http",
      "Url": "https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-kaiv-docker-facts -t streamable-http -u 'https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39'
```

### Other

```json
{
  "mcpServers": {
    "ai-kaiv-docker-facts": {
      "type": "http",
      "url": "https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39"
    }
  }
}
```

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-18 (score 82, +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-16 (score 81, +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-14 (score 80, +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 79, +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-09-10 (score 78, +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-09-08 (score 77, +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-09-06 (score 76, +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-09-05 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `check_image_tag` (~163 tokens)

Check Image Tag

Does this image:tag exist, how big is it, and which platforms does it cover?

Use this before writing a FROM line or a compose file. On a hit it returns size, platforms, arm64/amd64 support and the digest. On a miss it says whether the IMAGE exists but the tag is wrong, and lists real tags newest first so the caller can correct itself. Defaults to tag "latest" when none is given.

Input parameters:

- `name` (string, required): Docker image name as you would write it in a FROM line: "node", "postgres", "grafana/grafana". Official images may omit the "library/" prefix.
- `tag` (string): Tag to check, e.g. "20-alpine". Defaults to "latest".

Output parameters:

- `available_tags` (array): Present only on a miss: real tags, newest first, so the caller can correct itself.
- `digest` (string): Content digest, for pinning.
- `exists` (boolean): Whether this exact image:tag exists on Docker Hub.
- `image` (string)
- `image_exists` (boolean): Present only on a miss. Distinguishes a wrong tag from a wrong image name.
- `last_updated` (string): When the tag was last pushed (ISO 8601). A tag untouched for years is usually the wrong choice.
- `meaning` (string): One sentence, safe to show a user verbatim.
- `platforms` (array): os/arch strings this tag was built for, e.g. "linux/arm64".
- `reference` (string): The full reference, safe to paste into a FROM line.
- `size_mb` (number): Compressed size in MB.
- `status` (string): Docker Hub tag status, e.g. "active".
- `suggestion` (string): Present only on a miss: the most recently updated real tag.
- `supports_amd64` (boolean)
- `supports_arm64` (boolean): Answers the Apple Silicon and Graviton question directly.
- `tag` (string)

### `get_image_info` (~90 tokens)

Get Image Info

Repository facts: official status, pulls, stars, whether it is archived.

Use to judge whether an image is the canonical one and still maintained. Archived images still pull but receive no security patches.

Input parameters:

- `name` (string, required): Docker image name as you would write it in a FROM line: "node", "postgres", "grafana/grafana". Official images may omit the "library/" prefix.

Output parameters:

- `description` (string)
- `exists` (boolean)
- `hub_url` (string): Page a human can open.
- `image` (string)
- `is_archived` (boolean): Archived images still pull but receive no further updates, including security patches.
- `last_updated` (string)
- `official` (boolean): True for Docker Official Images (the "library" namespace).
- `pulls` (integer)
- `stars` (integer)

### `list_image_tags` (~114 tokens)

List Image Tags

Real tags for an image, most recently updated first.

Use when choosing a tag rather than verifying one. Each entry carries size and platform list, so a choice can be made without a second call.

Input parameters:

- `limit` (integer): How many tags to return, 1 to 100. Defaults to 25.
- `name` (string, required): Docker image name as you would write it in a FROM line: "node", "postgres", "grafana/grafana". Official images may omit the "library/" prefix.

Output parameters:

- `count` (integer)
- `exists` (boolean)
- `image` (string)
- `newest_first` (boolean): Tags are ordered by last update, most recent first.
- `tags` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-kaiv-docker-facts/api-bridge-mcp-docker-facts-adc41b39#diagnostics

## Score history

- 2026-09-20: 82
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 81
- 2026-09-16: 81
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 79
- 2026-09-12: 79
- 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: 75
- 2026-09-04: 75

## Common questions

### What is the ai.kaiv/docker-facts MCP server?

ai.kaiv/docker-facts is an MCP server listed in the public MCP registry as ai.kaiv/docker-facts. Does that Docker tag actually exist? Real tags, sizes and platforms, live from Docker Hub. This page covers its hosted endpoint (https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39).

### Is the ai.kaiv/docker-facts MCP server safe to use?

ai.kaiv/docker-facts scores 82 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 ai.kaiv/docker-facts MCP server expose?

ai.kaiv/docker-facts exposes 3 tools: check_image_tag, get_image_info, list_image_tags. Their descriptions and schemas cost roughly 367 tokens of context every time the server is loaded.

### Does the ai.kaiv/docker-facts MCP server require authentication?

No. We connected to ai.kaiv/docker-facts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ai.kaiv/docker-facts MCP server still maintained?

ai.kaiv/docker-facts is still listed as active in the MCP registry. We last reached this channel on 20 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://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39
- Changelog RSS feed: https://verifymcp.io/servers/ai-kaiv-docker-facts/api-bridge-mcp-docker-facts-adc41b39.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-kaiv-docker-facts/api-bridge-mcp-docker-facts-adc41b39.json
- HTML version of this page: https://verifymcp.io/servers/ai-kaiv-docker-facts/api-bridge-mcp-docker-facts-adc41b39