ai.kaiv/docker-facts
REMOTE · API.KAIV.AI · SCANNED SEP 20
Does that Docker tag actually exist? Real tags, sizes and platforms, live from Docker Hub.
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · api.kaiv.ai
claude mcp add --transport http ai-kaiv-docker-facts 'https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39'
{
"mcpServers": {
"ai-kaiv-docker-facts": {
"url": "https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39"
}
}
} {
"servers": {
"ai-kaiv-docker-facts": {
"type": "http",
"url": "https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39"
}
}
} [mcp_servers.ai-kaiv-docker-facts] url = "https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39"
{
"$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 mcp add ai-kaiv-docker-facts --url 'https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39' --transport streamable-http
mcp_servers:
ai-kaiv-docker-facts:
url: "https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39" {
"McpServers": {
"ai-kaiv-docker-facts": {
"Transport": "http",
"Url": "https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39"
}
}
} assistant mcp add ai-kaiv-docker-facts -t streamable-http -u 'https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
- 6 Sept 26 +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.
- 5 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kaiv.ai | CN=WE1,O=Google Trust Services,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b225111947d906a40e56536076ff66c0 |
| SANs: kaiv.ai, *.kaiv.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.kaiv.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| kaiv.ai. | present | 2371 | 13 | Verified |
| api.kaiv.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self';form-action 'self' https://auth.kaiv.ai;script-src 'self' https://cdnjs.cloudflare.com https://challenges.cloudflare.com 'unsafe-inline';style-src 'self' https://cdnjs.cloudflare.com 'unsafe-inline';img-src 'self' data: blob:;connect-src 'self' https://api.openai.com https://api.anthropic.com https://generativelanguage.googleapis.com https://challenges.cloudflare.com https://*.kaiv.ai;frame-src 'self' https://challenges.cloudflare.com;font-src 'self' https://cdnjs.cloudflare.com;object-src 'none';media-src 'self';base-uri 'self';frame-ancestors 'self';script-src-attr 'none';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39 | Verified | 200 | |
| http (plaintext) | http://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39 | HTTPS enforced | 301 | https://api.kaiv.ai/api/bridge/mcp/docker-facts-adc41b39 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_image_tag Check Image Tag ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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". |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Whether this exact image:tag exists on Docker Hub. |
| image | string | yes | – |
| 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 | yes | 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 | yes | – |
No examples provided.
get_image_info Get Image Info ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Docker image name as you would write it in a FROM line: "node", "postgres", "grafana/grafana". Official images may omit the "library/" prefix. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No examples provided.
list_image_tags List Image Tags ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many tags to return, 1 to 100. Defaults to 25. |
| name | string | yes | Docker image name as you would write it in a FROM line: "node", "postgres", "grafana/grafana". Official images may omit the "library/" prefix. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| exists | boolean | – | – |
| image | string | – | – |
| newest_first | boolean | – | Tags are ordered by last update, most recent first. |
| tags | array | – | – |
No examples provided.
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.