# Dependency check (remote · deps.bestsmartgoods.com)

Check a package version for known vulnerabilities and Packagist release facts.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `deps.bestsmartgoods.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/ladanyin-dependency-check/deps.md), [page](https://verifymcp.io/servers/ladanyin-dependency-check/deps)

## Channel facts

- Endpoint: `https://deps.bestsmartgoods.com/mcp`
- 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-11-05.

- **Endpoint Security**: 74/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 425 tokens (~212/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Dependency check MCP server?

Dependency check is a hosted endpoint at https://deps.bestsmartgoods.com/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 ladanyin-dependency-check 'https://deps.bestsmartgoods.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ladanyin-dependency-check": {
      "url": "https://deps.bestsmartgoods.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ladanyin-dependency-check": {
      "type": "http",
      "url": "https://deps.bestsmartgoods.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ladanyin-dependency-check]
url = "https://deps.bestsmartgoods.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ladanyin-dependency-check": {
      "type": "remote",
      "url": "https://deps.bestsmartgoods.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ladanyin-dependency-check --url 'https://deps.bestsmartgoods.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ladanyin-dependency-check:
    url: "https://deps.bestsmartgoods.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ladanyin-dependency-check": {
      "Transport": "http",
      "Url": "https://deps.bestsmartgoods.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ladanyin-dependency-check -t streamable-http -u 'https://deps.bestsmartgoods.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ladanyin-dependency-check": {
      "type": "http",
      "url": "https://deps.bestsmartgoods.com/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-11-05 (score 71)

First indexed and scored.

## MCP tools (2)

### `check_package` (~180 tokens)

Check a Packagist package

Read the current Packagist facts for one PHP package: latest stable version, required PHP, license, and whether it is abandoned. Use it before composer require. Send vendor/package. Set version to ask about one release; version_found is false when that release is absent, and the latest stable is still returned. This does not list vulnerabilities. The first 5 successful calls each UTC day from one network address are free and need no key. not_found and fetch_failed are not charged and do not use a free call. After the 5, send X-API-Key. A key call costs 0.04 credit on success. Key: https://firm.bestsmartgoods.com/signup

Input parameters:

- `name` (string, required): Packagist name, vendor/package.
- `version` (string): Optional release to select. Omit it for the latest stable.

### `check_dependency` (~245 tokens)

Check a dependency for known vulnerabilities

Look up known vulnerabilities for one package version from OSV. Returns advisory id, summary, CVE aliases, severity string, and fixed versions when the advisory lists them. Ecosystems: packagist, npm, pypi, go, crates.io, maven, rubygems, nuget. Omit ecosystem and a vendor/package name uses Packagist, otherwise npm. An empty list means OSV returned none, and that successful lookup is charged. This is not a full audit. The first 5 successful calls each UTC day from one network address are free and need no key. not_found and fetch_failed are not charged and do not use a free call. After the 5, send X-API-Key. A key call costs 0.04 credit on success. Key: https://firm.bestsmartgoods.com/signup

Input parameters:

- `ecosystem` (string): OSV ecosystem. Omit it and a vendor/package name uses Packagist, otherwise npm.
- `name` (string, required): Package name, for example guzzlehttp/guzzle or lodash.
- `version` (string, required): The exact version to check, for example 6.5.0.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ladanyin-dependency-check/deps#diagnostics

## Score history

- 2026-11-05: 71

## Common questions

### What is the Dependency check MCP server?

Dependency check is an MCP server listed in the public MCP registry as io.github.ladanyin/dependency-check. Check a package version for known vulnerabilities and Packagist release facts. This page covers its hosted endpoint (https://deps.bestsmartgoods.com/mcp).

### Is the Dependency check MCP server safe to use?

Dependency check scores 71 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 Dependency check MCP server expose?

Dependency check exposes 2 tools: check_package, check_dependency. Their descriptions and schemas cost roughly 425 tokens of context every time the server is loaded.

### Does the Dependency check MCP server require authentication?

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

### Is the Dependency check MCP server still maintained?

Dependency check is still listed as active in the MCP registry. We last reached this channel on 5 November 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://deps.bestsmartgoods.com/mcp
- Authorisation metadata: https://deps.bestsmartgoods.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/ladanyin/agentlane
- Website: https://deps.bestsmartgoods.com/docs
- Changelog RSS feed: https://verifymcp.io/servers/ladanyin-dependency-check/deps.xml
- Changelog JSON feed: https://verifymcp.io/servers/ladanyin-dependency-check/deps.json
- HTML version of this page: https://verifymcp.io/servers/ladanyin-dependency-check/deps