io.github.cyanheads/osv-advisory-mcp-server
REMOTE · OSV-ADVISORY.CASEYJHAND.COM · 2 COMPONENTS · SCANNED SEP 28
Query OSV.dev for package vulnerabilities and batch-audit dependency lists via MCP.
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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 821 tokens (~205/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 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 io.github.cyanheads/osv-advisory-mcp-server server?
io.github.cyanheads/osv-advisory-mcp-server is a hosted endpoint at https://osv-advisory.caseyjhand.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.
remote · osv-advisory.caseyjhand.com
claude mcp add --transport http cyanheads-osv-advisory-mcp-server 'https://osv-advisory.caseyjhand.com/mcp'
{
"mcpServers": {
"cyanheads-osv-advisory-mcp-server": {
"url": "https://osv-advisory.caseyjhand.com/mcp"
}
}
} {
"servers": {
"cyanheads-osv-advisory-mcp-server": {
"type": "http",
"url": "https://osv-advisory.caseyjhand.com/mcp"
}
}
} [mcp_servers.cyanheads-osv-advisory-mcp-server] url = "https://osv-advisory.caseyjhand.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cyanheads-osv-advisory-mcp-server": {
"type": "remote",
"url": "https://osv-advisory.caseyjhand.com/mcp",
"enabled": true
}
}
} openclaw mcp add cyanheads-osv-advisory-mcp-server --url 'https://osv-advisory.caseyjhand.com/mcp' --transport streamable-http
mcp_servers:
cyanheads-osv-advisory-mcp-server:
url: "https://osv-advisory.caseyjhand.com/mcp" {
"McpServers": {
"cyanheads-osv-advisory-mcp-server": {
"Transport": "http",
"Url": "https://osv-advisory.caseyjhand.com/mcp"
}
}
} assistant mcp add cyanheads-osv-advisory-mcp-server -t streamable-http -u 'https://osv-advisory.caseyjhand.com/mcp'
{
"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.
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.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 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
- 24 Sept 26 0
- Tool “osv_query_package” rewrote its description, which is the text the model reads security
- Tool “osv_list_ecosystems” rewrote its description, which is the text the model reads security
- Server version: 0.1.14 → 0.1.15 functional
- “osv_get_vulnerability” reworded the description of “id” cosmetic
- 20 Sept 26 0
- Server version: 0.1.13 → 0.1.14 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 −1
- Stability: pass → 0.93 functional
- 26 Aug 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
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 28 Sept 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 | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a6985204ed51ae050e7738aa6be668e9 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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 →
osv_get_vulnerability Osv Get Vulnerability ~221
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | One exact, complete OSV advisory ID from any OSV source database, matched case-sensitively. Prefixes include "GHSA-" (GitHub), "PYSEC-" (PyPI), "RUSTSEC-" (Rust), "GO-" (Go), "DSA-"/"DLA-" (Debian),… |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| error | object | – | Present when the call failed. Absent on success. |
| 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 | – | Record-level severity entries (CVSS vectors, Ubuntu priorities). Empty for unscored advisories and for advisories that score each affected package separately. |
| severityLabel | string|null | – | Severity label ("LOW", "MODERATE", "HIGH", "CRITICAL") from the first source that yields one: database_specific.severity, an Ubuntu priority, then the highest CVSS v3/v4 score (0.1–3.9 LOW, 4.0–6.9 M… |
| severitySource | – | – | The severity entry severityLabel was derived from. Null exactly when the label is. |
| 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. |
No examples provided.
osv_list_ecosystems Osv List Ecosystems ~121
Return the supported ecosystem identifier strings for osv_query_package and osv_query_batch: every ecosystem the OSV schema names that OSV.dev accepts at query time, plus GIT, as verified on 2026-09-24. 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 and may lag ecosystems added after that date.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| error | object | – | Present when the call failed. Absent on success. |
| note | string | – | 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.
| 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. |
| error | object | – | Present when the call failed. Absent on success. |
| 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. |
No examples provided.
osv_query_package Osv Query Package ~218
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 the fixed versions listed for the queried package. 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.
| 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. |
| error | object | – | Present when the call failed. Absent on success. |
| 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. |
No examples provided.
What is the io.github.cyanheads/osv-advisory-mcp-server server?
io.github.cyanheads/osv-advisory-mcp-server is listed in the public MCP registry as io.github.cyanheads/osv-advisory-mcp-server. Query OSV.dev for package vulnerabilities and batch-audit dependency lists via MCP. This page covers its hosted endpoint (https://osv-advisory.caseyjhand.com/mcp).
Is the io.github.cyanheads/osv-advisory-mcp-server server safe to use?
io.github.cyanheads/osv-advisory-mcp-server scores 88 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 io.github.cyanheads/osv-advisory-mcp-server server expose?
io.github.cyanheads/osv-advisory-mcp-server exposes 4 tools: osv_list_ecosystems, osv_query_package, osv_get_vulnerability, osv_query_batch. Their descriptions and schemas cost roughly 673 tokens of context every time the server is loaded.
Does the io.github.cyanheads/osv-advisory-mcp-server server require authentication?
No. We connected to io.github.cyanheads/osv-advisory-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.cyanheads/osv-advisory-mcp-server server still maintained?
io.github.cyanheads/osv-advisory-mcp-server is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.