ai.kaiv/version-truth
REMOTE · API.KAIV.AI · SCANNED SEP 20
Latest versions, LTS windows, and EOL dates for 300+ products. Fresh ground truth for stale models.
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 Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 379 tokens (~126/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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/version-truth MCP server?
ai.kaiv/version-truth is a hosted endpoint at https://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c, 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-version-truth 'https://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c'
{
"mcpServers": {
"ai-kaiv-version-truth": {
"url": "https://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c"
}
}
} {
"servers": {
"ai-kaiv-version-truth": {
"type": "http",
"url": "https://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c"
}
}
} [mcp_servers.ai-kaiv-version-truth] url = "https://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-kaiv-version-truth": {
"type": "remote",
"url": "https://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c",
"enabled": true
}
}
} openclaw mcp add ai-kaiv-version-truth --url 'https://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c' --transport streamable-http
mcp_servers:
ai-kaiv-version-truth:
url: "https://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c" {
"McpServers": {
"ai-kaiv-version-truth": {
"Transport": "http",
"Url": "https://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c"
}
}
} assistant mcp add ai-kaiv-version-truth -t streamable-http -u 'https://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c'
{
"mcpServers": {
"ai-kaiv-version-truth": {
"type": "http",
"url": "https://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c"
}
}
} 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.
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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/version-truth-ca7b5b8c
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/version-truth-ca7b5b8c | Verified | 200 | |
| http (plaintext) | http://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c | HTTPS enforced | 301 | https://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c |
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 →
get_cycle Get Cycle ~112
One release cycle of a product: its latest patch version, release date, LTS/support/EOL dates and whether extended support exists. Use when you already know the major version, e.g. product=nodejs cycle=24. Answers: is Node 18 still supported? What is the newest 24.x patch?
| Name | Type | Req | Description |
|---|---|---|---|
| cycle | string | yes | Release cycle / major version, e.g. '24' or '3.12' |
| product | string | yes | Product slug, e.g. 'nodejs' |
No output schema declared.
No examples provided.
get_product Get Product ~122
All release cycles for a product, newest first: latest patch version, release date, LTS status/date, end-of-life date, and end of active support. Answers: what is the CURRENT version of X? Which major versions are still supported? When does version Y reach EOL? Use exact slugs from list_products (e.g. nodejs, python, django, postgresql, ubuntu, amazon-eks).
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | Product slug from list_products, e.g. 'nodejs', 'python', 'react', 'postgresql' |
No output schema declared.
No examples provided.
list_products List Products ~44
List every product slug tracked (nodejs, python, react, postgresql, ubuntu, …). Call this first when unsure of the exact product slug to pass to get_product.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the ai.kaiv/version-truth MCP server?
ai.kaiv/version-truth is an MCP server listed in the public MCP registry as ai.kaiv/version-truth. Latest versions, LTS windows, and EOL dates for 300+ products. Fresh ground truth for stale models. This page covers its hosted endpoint (https://api.kaiv.ai/api/bridge/mcp/version-truth-ca7b5b8c).
Is the ai.kaiv/version-truth MCP server safe to use?
ai.kaiv/version-truth scores 91 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/version-truth MCP server expose?
ai.kaiv/version-truth exposes 3 tools: get_cycle, get_product, list_products. Their descriptions and schemas cost roughly 278 tokens of context every time the server is loaded.
Does the ai.kaiv/version-truth MCP server require authentication?
No. We connected to ai.kaiv/version-truth without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.kaiv/version-truth MCP server still maintained?
ai.kaiv/version-truth 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.