ai.kaiv/dependency-trust
REMOTE · API.KAIV.AI · SCANNED SEP 20
Trust-check any dependency for agents: OpenSSF Scorecard, licenses, CVEs, deps. 7 ecosystems.
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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 890 tokens (~178/item across 5 items; 5 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 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
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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/dependency-trust MCP server?
ai.kaiv/dependency-trust is a hosted endpoint at https://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d, 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-dependency-trust 'https://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d'
{
"mcpServers": {
"ai-kaiv-dependency-trust": {
"url": "https://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d"
}
}
} {
"servers": {
"ai-kaiv-dependency-trust": {
"type": "http",
"url": "https://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d"
}
}
} [mcp_servers.ai-kaiv-dependency-trust] url = "https://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-kaiv-dependency-trust": {
"type": "remote",
"url": "https://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d",
"enabled": true
}
}
} openclaw mcp add ai-kaiv-dependency-trust --url 'https://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d' --transport streamable-http
mcp_servers:
ai-kaiv-dependency-trust:
url: "https://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d" {
"McpServers": {
"ai-kaiv-dependency-trust": {
"Transport": "http",
"Url": "https://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d"
}
}
} assistant mcp add ai-kaiv-dependency-trust -t streamable-http -u 'https://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d'
{
"mcpServers": {
"ai-kaiv-dependency-trust": {
"type": "http",
"url": "https://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d"
}
}
} 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.
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 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.
- 12 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.
- 10 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.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 0
- Tool “get_advisory” rewrote its description, which is the text the model reads security
- Tool “get_dependencies” rewrote its description, which is the text the model reads security
- Tool “get_project_health” rewrote its description, which is the text the model reads security
- Tool “get_advisory” now declares an output schema ▲ functional
- Tool “get_dependencies” now declares an output schema ▲ functional
- Tool “get_package” now declares an output schema ▲ functional
- Tool “get_package_version” now declares an output schema ▲ functional
- Tool “get_project_health” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- 5 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.
- 3 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.
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/dependency-trust-f1aaf06d
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/dependency-trust-f1aaf06d | Verified | 200 | |
| http (plaintext) | http://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d | HTTPS enforced | 301 | https://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d |
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_advisory Get Advisory ~154
Get a security advisory (vulnerability) by its key. Returns a security advisory by key, for example a GHSA id taken from a version's advisoryKeys, including the title, CVE aliases, CVSS v3 score and vector, and a link to the full record on osv.dev. Use this only when you already have an advisory ID from get_package_version's advisoryKeys. There is no search here. To find out whether a version has vulnerabilities at all, call get_package_version first; this tool explains one advisory in depth.
| Name | Type | Req | Description |
|---|---|---|---|
| advisoryKey | string | yes | Advisory id, e.g. 'GHSA-29mw-wpgm-hmr9' (taken from a version's advisoryKeys). |
Structured output declared, but exposes no named fields.
No examples provided.
get_dependencies Get Dependencies ~137
Get the resolved dependency graph for one package version. Returns the full resolved dependency graph (direct and indirect) for a version. Each node has the dependency's exact version and its relation (SELF / DIRECT / INDIRECT). Use it to reason about transitive dependencies and supply chain.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | Package name, raw and unencoded (the gateway URL-encodes it). Use scoped or namespaced names as-is, e.g. npm '@angular/core', Maven 'group:artifact'. |
| system | string | yes | Package ecosystem. |
| version | string | yes | Exact version string, e.g. '18.2.0'. |
Structured output declared, but exposes no named fields.
No examples provided.
get_package Get Package ~122
List every version of a package and whether each is deprecated. Returns all published versions of a package with publish date, the default-version flag, and deprecation status. Use it to find the latest version or check if a package is deprecated. Coding agents should call this before recommending a package or version.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | Package name, raw and unencoded (the gateway URL-encodes it). Use scoped or namespaced names as-is, e.g. npm '@angular/core', Maven 'group:artifact'. |
| system | string | yes | Package ecosystem. |
Structured output declared, but exposes no named fields.
No examples provided.
get_package_version Get Package Version ~153
Get license, security advisories, and source links for one package version. Returns detailed metadata for a single version: SPDX licenses, security advisoryKeys (known vulnerabilities), homepage/issue-tracker/source-repo links, registries, publish date, and deprecation status. Pass any advisoryKey returned here to get_advisory for the vulnerability details.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | Package name, raw and unencoded (the gateway URL-encodes it). Use scoped or namespaced names as-is, e.g. npm '@angular/core', Maven 'group:artifact'. |
| system | string | yes | Package ecosystem. |
| version | string | yes | Exact version string, e.g. '18.2.0'. |
Structured output declared, but exposes no named fields.
No examples provided.
get_project_health Get Project Health ~223
Get a project's OpenSSF Scorecard security posture and maintenance signals. THE trust check. Returns supply-chain trust signals for a package's source repository: the OpenSSF Scorecard overall score (0-10) and per-check results (Maintained, Code-Review, Signed-Releases, Branch-Protection, Pinned-Dependencies, Dangerous-Workflow, Token-Permissions, Security-Policy, Vulnerabilities, ...), plus stars, forks, open-issue count, and license. Use it to judge whether a dependency is actively maintained and securely operated, not just whether it has a known CVE. Get the projectKey from a version's SOURCE_REPO link (call get_package_version first), e.g. 'github.com/facebook/react'.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | yes | Source repository, raw and unencoded (the gateway URL-encodes it). Pass it as-is, e.g. 'github.com/facebook/react'. Supported hosts: github.com, gitlab.com, bitbucket.org. Take it from a version's SO… |
Structured output declared, but exposes no named fields.
No examples provided.
What is the ai.kaiv/dependency-trust MCP server?
ai.kaiv/dependency-trust is an MCP server listed in the public MCP registry as ai.kaiv/dependency-trust. Trust-check any dependency for agents: OpenSSF Scorecard, licenses, CVEs, deps. 7 ecosystems. This page covers its hosted endpoint (https://api.kaiv.ai/api/bridge/mcp/dependency-trust-f1aaf06d).
Is the ai.kaiv/dependency-trust MCP server safe to use?
ai.kaiv/dependency-trust scores 89 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/dependency-trust MCP server expose?
ai.kaiv/dependency-trust exposes 5 tools: get_advisory, get_dependencies, get_package, get_package_version, get_project_health. Their descriptions and schemas cost roughly 789 tokens of context every time the server is loaded.
Does the ai.kaiv/dependency-trust MCP server require authentication?
No. We connected to ai.kaiv/dependency-trust without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.kaiv/dependency-trust MCP server still maintained?
ai.kaiv/dependency-trust 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.