io.github.cyanheads/osv-advisory-mcp-server

REMOTE · OSV-ADVISORY.CASEYJHAND.COM · 2 COMPONENTS · SCANNED AUG 3

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

Available components

remote · osv-advisory.caseyjhand.com 69 npm · @cyanheads/osv-advisory-mcp-server 35

+5 this week 69 69 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security66

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
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. See how to fix → View diagnostics → Unverified
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 Usability68

AI-judged instruction clarity (excellent).Pass
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. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · osv-advisory.caseyjhand.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 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.

3 Aug 26 +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.
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +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.
28 Jul 26 +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.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 64

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Probed https://osv-advisory.caseyjhand.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=caseyjhand.com	CN=WE1,O=Google Trust Services,C=US	7 Jul 2026	5 Oct 2026	ECDSA 256	ECDSA-SHA256	5aad900eb2055a0b0ea55912ec19680c
SANs: caseyjhand.com, *.caseyjhand.com
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

DNSSEC secure

Validation of osv-advisory.caseyjhand.com. — Secure

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
caseyjhand.com.	present	2371	13	Verified
osv-advisory.caseyjhand.com.				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=63072000; includeSubDomains; preload
x-content-type-options	nosniff

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://osv-advisory.caseyjhand.com/mcp	Verified	200
http (plaintext)	http://osv-advisory.caseyjhand.com/mcp	HTTPS enforced	301	https://osv-advisory.caseyjhand.com/mcp

MCP tools — 4 exposed · ~604 tokens

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.

Tool Tokens

osv_get_vulnerability Osv Get Vulnerability ~175

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 Output Examples

Name	Type	Req	Description
id	string	yes	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".

Name	Type	Req	Description
affected	array	yes	All affected packages and their version ranges. An advisory may span multiple packages or ecosystems.
aliases	array	yes	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	yes	CWE weakness classifications (e.g. ["CWE-79"]). Present on GitHub Advisory Database records; empty otherwise.
details	string	yes	Full advisory text, typically in Markdown. May include proof-of-concept, reproduction steps, or remediation guidance.
id	string	yes	OSV vulnerability ID.
modified	string	yes	ISO 8601 timestamp of last modification.
published	string	yes	ISO 8601 timestamp when published.
references	array	yes	Advisory references — NVD links, patches, vendor advisories, PoC reports.
schemaVersion	string	yes	OSV schema version this record conforms to (e.g. "1.7.3").
severity	array	yes	CVSS severity entries. Empty for unscored advisories.
severityLabel	—	yes	Human-readable severity label ("LOW", "MODERATE", "HIGH", "CRITICAL"). Present on GHSA-sourced records; null when not available.
summary	string	yes	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.

No examples provided.

osv_list_ecosystems Osv List Ecosystems ~103

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.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
ecosystems	array	yes	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	yes	Advisory note about list currency and canonical source.

No examples provided.

osv_query_batch Osv Query Batch ~113

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 Output Examples

Name	Type	Req	Description
packages	array	yes	Packages to audit. One entry per dependency. Positional: result[i] corresponds to packages[i].

Name	Type	Req	Description
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	yes	Per-package results, positionally matching the input array.
summary	object	yes	Aggregate statistics across the full batch.

No examples provided.

osv_query_package Osv Query Package ~213

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 Output Examples

Name	Type	Req	Description
ecosystem	string	yes	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	yes	Package name as it appears in the ecosystem (e.g. "express", "requests", "serde"). Case-sensitive.
version	string	yes	Package version to check (e.g. "4.17.1", "3.1.4", "1.0.0"). Must be an exact version string, not a range.

Name	Type	Req	Description
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	yes	Query parameters as submitted.
truncated	boolean	yes	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	yes	Vulnerabilities matching this package version. An empty array means no known vulnerabilities ONLY when truncated is false.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	64
27 Jul	64
28 Jul	65
29 Jul	66
30 Jul	66
31 Jul	68
1 Aug	68
2 Aug	68
3 Aug	69