# io.github.cyanheads/osv-advisory-mcp-server (remote · osv-advisory.caseyjhand.com)

Query OSV.dev for package vulnerabilities and batch-audit dependency lists via MCP.

- Trust score: 69/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `osv-advisory.caseyjhand.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/cyanheads-osv-advisory-mcp-server/osv-advisory.md), [page](https://verifymcp.io/servers/cyanheads-osv-advisory-mcp-server/osv-advisory)
- npm · `@cyanheads/osv-advisory-mcp-server`: 35/100, [markdown](https://verifymcp.io/servers/cyanheads-osv-advisory-mcp-server/cyanheads-osv-advisory-mcp-server.md), [page](https://verifymcp.io/servers/cyanheads-osv-advisory-mcp-server/cyanheads-osv-advisory-mcp-server)

## Channel facts

- Endpoint: `https://osv-advisory.caseyjhand.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.12`

## 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-08-03.

- **Endpoint Security**: 66/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 4 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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 752 tokens (~188/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http cyanheads-osv-advisory-mcp-server https://osv-advisory.caseyjhand.com/mcp
```

### Codex

```toml
[mcp_servers.cyanheads-osv-advisory-mcp-server]
url = "https://osv-advisory.caseyjhand.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-osv-advisory-mcp-server": {
      "type": "remote",
      "url": "https://osv-advisory.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cyanheads-osv-advisory-mcp-server --url https://osv-advisory.caseyjhand.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cyanheads-osv-advisory-mcp-server:
    url: "https://osv-advisory.caseyjhand.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "cyanheads-osv-advisory-mcp-server": {
      "type": "http",
      "url": "https://osv-advisory.caseyjhand.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-08-03 (score 69, +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.

### 2026-07-31 (score 68, +2)

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

### 2026-07-30 (score 66, 0)

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

### 2026-07-29 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 65, +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.

### 2026-07-27 (score 64, 0)

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

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (4)

### `osv_list_ecosystems` (~103 tokens)

Osv List Ecosystems

Return the list of supported ecosystem identifier strings for use with osv_query_package and osv_query_batch. Ecosystem strings are case-sensitive exact matches — passing "pypi" instead of "PyPI" returns an error from the API. Use this tool to discover valid ecosystem strings before querying, or to verify an ecosystem identifier from a lockfile format. The list is static (maintained from the OSV schema spec) and may occasionally lag newly added ecosystems.

Output parameters:

- `ecosystems` (array): Supported ecosystem identifier strings. These are case-sensitive exact matches required by the ecosystem parameter of osv_query_package and osv_query_batch.
- `note` (string): Advisory note about list currency and canonical source.

### `osv_query_package` (~213 tokens)

Osv Query Package

Query known vulnerabilities for a single package version across any supported ecosystem. Returns all matching OSV advisories with severity (CVSS vectors), CVE aliases, affected version ranges, and first safe version. Use osv_list_ecosystems to validate the ecosystem string before querying — ecosystem strings are case-sensitive exact matches and an invalid value returns an error, not empty results.

Input parameters:

- `ecosystem` (string, required): Ecosystem identifier. Must be an exact match (case-sensitive). Use osv_list_ecosystems to see valid values. Examples: "npm", "PyPI", "crates.io", "Go", "Maven", "NuGet".
- `name` (string, required): Package name as it appears in the ecosystem (e.g. "express", "requests", "serde"). Case-sensitive.
- `version` (string, required): Package version to check (e.g. "4.17.1", "3.1.4", "1.0.0"). Must be an exact version string, not a range.

Output parameters:

- `effectiveQuery` (string): The package@version (ecosystem) tuple as queried, echoed for content-only clients.
- `notice` (string): Present on the clean path — confirms no known vulnerabilities for the queried package.
- `queryMeta` (object): Query parameters as submitted.
- `truncated` (boolean): True when OSV returned more result pages than the fetch cap could follow — the vulnerability list may be INCOMPLETE. A truncated empty list is NOT a clean result; raise OSV_QUERY_MAX_PAGES or narrow…
- `vulns` (array): Vulnerabilities matching this package version. An empty array means no known vulnerabilities ONLY when truncated is false.

### `osv_get_vulnerability` (~175 tokens)

Osv Get Vulnerability

Fetch the full advisory record for an OSV vulnerability ID. Returns the complete record: summary, full details text, CVE aliases, all affected packages and version ranges, fix versions, CVSS severity vectors, CWE weakness IDs, and references. Use when osv_query_package or osv_query_batch returns a vuln ID and you need the full advisory context — eligibility criteria, scope of affected packages, or remediation guidance.

Input parameters:

- `id` (string, required): OSV vulnerability ID. Accepts any prefix: "GHSA-" (GitHub), "PYSEC-" (Python), "RUSTSEC-" (Rust), "GO-" (Go), "DSA-"/"DLA-" (Debian), "CVE-" (fallback direct lookups). Example: "GHSA-29mw-wpgm-hmr9".

Output parameters:

- `affected` (array): All affected packages and their version ranges. An advisory may span multiple packages or ecosystems.
- `aliases` (array): Alternative IDs — usually CVE IDs. Accepted by nvd_get_cve on nist-nvd-mcp-server for CVSS base score, EPSS exploitation probability, and CISA KEV status.
- `cweIds` (array): CWE weakness classifications (e.g. ["CWE-79"]). Present on GitHub Advisory Database records; empty otherwise.
- `details` (string): Full advisory text, typically in Markdown. May include proof-of-concept, reproduction steps, or remediation guidance.
- `id` (string): OSV vulnerability ID.
- `modified` (string): ISO 8601 timestamp of last modification.
- `published` (string): ISO 8601 timestamp when published.
- `references` (array): Advisory references — NVD links, patches, vendor advisories, PoC reports.
- `schemaVersion` (string): OSV schema version this record conforms to (e.g. "1.7.3").
- `severity` (array): CVSS severity entries. Empty for unscored advisories.
- `severityLabel`: Human-readable severity label ("LOW", "MODERATE", "HIGH", "CRITICAL"). Present on GHSA-sourced records; null when not available.
- `summary` (string): One-line advisory description.
- `withdrawn` (string): ISO 8601 timestamp when this advisory was withdrawn. Present ONLY on withdrawn advisories — a withdrawn record has been retracted and must not be treated as an active vulnerability.

### `osv_query_batch` (~113 tokens)

Osv Query Batch

Query vulnerabilities for multiple packages in one call — the primary tool for dependency audits, SBOM scanning, and lockfile triage. Pass an array of {name, ecosystem, version} tuples (up to 1000). Each entry in the response corresponds positionally to the input. Each finding includes CVE aliases for chaining to nist-nvd-mcp-server for CVSS scoring.

Input parameters:

- `packages` (array, required): Packages to audit. One entry per dependency. Positional: result[i] corresponds to packages[i].

Output parameters:

- `effectiveQuery` (string): Compact scan summary (package and outcome counts), echoed on edge-case batches for content-only clients.
- `notice` (string): Present on all-clean or all-errors batches — the aggregate outcome for content-only clients.
- `results` (array): Per-package results, positionally matching the input array.
- `summary` (object): Aggregate statistics across the full batch.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cyanheads-osv-advisory-mcp-server/osv-advisory#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 68
- 2026-07-31: 68
- 2026-07-30: 66
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://osv-advisory.caseyjhand.com/mcp
- Repository: https://github.com/cyanheads/osv-advisory-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/cyanheads-osv-advisory-mcp-server/osv-advisory/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyanheads-osv-advisory-mcp-server/osv-advisory/changelog.json
- HTML version of this page: https://verifymcp.io/servers/cyanheads-osv-advisory-mcp-server/osv-advisory