# Depcheck (remote · depcheck.kaneky.dev)

Known vulnerabilities for exact package versions from OSV, with fixes. Paid per call, x402.

- Trust score: 59/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `depcheck.kaneky.dev`: 59/100 (this document), [markdown](https://verifymcp.io/servers/dev-kaneky-depcheck/depcheck.md), [page](https://verifymcp.io/servers/dev-kaneky-depcheck/depcheck)

## Channel facts

- Endpoint: `https://depcheck.kaneky.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-29.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 247 tokens (~247/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Depcheck MCP server?

Depcheck is a hosted endpoint at https://depcheck.kaneky.dev/mcp, 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 dev-kaneky-depcheck 'https://depcheck.kaneky.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-kaneky-depcheck": {
      "url": "https://depcheck.kaneky.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-kaneky-depcheck": {
      "type": "http",
      "url": "https://depcheck.kaneky.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-kaneky-depcheck]
url = "https://depcheck.kaneky.dev/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev-kaneky-depcheck --url 'https://depcheck.kaneky.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-kaneky-depcheck:
    url: "https://depcheck.kaneky.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-kaneky-depcheck": {
      "Transport": "http",
      "Url": "https://depcheck.kaneky.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-kaneky-depcheck -t streamable-http -u 'https://depcheck.kaneky.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-kaneky-depcheck": {
      "type": "http",
      "url": "https://depcheck.kaneky.dev/mcp"
    }
  }
}
```

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-28 (score 59, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 58, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-25 (score 57)

First indexed and scored.

## MCP tools (1)

### `check_packages` (~155 tokens)

Look up the known vulnerabilities affecting exact package versions in the public OSV database (npm, PyPI, Go, Maven, crates.io, RubyGems, NuGet, Packagist, Pub, Hex), 1 to 50 packages per call. Per package: every OSV advisory for that version with its id, CVE/GHSA aliases, summary, severity (database label, CVSS vectors, v3 base scores), the versions that fix it or "no fix published", published/modified dates and a link. Plus a summary: packages checked, packages vulnerable, total advisories and the highest severity. Evidence, not advice: absence from OSV does not prove safety.

Input parameters:

- `packages` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-kaneky-depcheck/depcheck#diagnostics

## Score history

- 2026-09-29: 59
- 2026-09-28: 59
- 2026-09-27: 58
- 2026-09-26: 58
- 2026-09-25: 57

## Common questions

### What is the Depcheck MCP server?

Depcheck is an MCP server listed in the public MCP registry as dev.kaneky/depcheck. Known vulnerabilities for exact package versions from OSV, with fixes. Paid per call, x402. This page covers its hosted endpoint (https://depcheck.kaneky.dev/mcp).

### Is the Depcheck MCP server safe to use?

Depcheck scores 59 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 Depcheck MCP server expose?

Depcheck exposes 1 tool: check_packages. Their descriptions and schemas cost roughly 155 tokens of context every time the server is loaded.

### Does the Depcheck MCP server require authentication?

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

### Is the Depcheck MCP server still maintained?

Depcheck is still listed as active in the MCP registry. We last reached this channel on 29 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://depcheck.kaneky.dev/mcp
- Website: https://depcheck.kaneky.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-kaneky-depcheck/depcheck.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-kaneky-depcheck/depcheck.json
- HTML version of this page: https://verifymcp.io/servers/dev-kaneky-depcheck/depcheck