Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.cyanheads/first-epss-mcp-server

REMOTE · FIRST-EPSS.CASEYJHAND.COM · 2 COMPONENTS

Look up FIRST EPSS scores and daily history, find CVEs by threshold, and prioritize them with CVSS.

+3 this week 80 Trust /100

Last scanned (10 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Security

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1449 tokens (~241/item across 6 items; 5 tools + 1 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 Management40
  • Stability observed for 12 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 29 Oct 26 +4
    • Tool “epss_query_threshold” rewrote its description, which is the text the model reads security
    • First check of Schema quality: 100 functional
    • New resource “first-epss-guide” functional
    • Server version: 0.1.3 → 0.2.0 functional
  • 27 Oct 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.

  • 25 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 24 Oct 26 71

    First indexed and scored.

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 5 Nov 2026 · Probed https://first-epss.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 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 995a30681ab772540e934241ca1d576c
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 first-epss.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
first-epss.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://first-epss.caseyjhand.com/mcp Verified 200
http (plaintext) http://first-epss.caseyjhand.com/mcp HTTPS enforced 301 https://first-epss.caseyjhand.com/mcp
MCP tools · 5 exposed · ~1,109 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. 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 →

Tool Tokens
epss_get_scores ~199

Retrieve latest available or historically dated FIRST EPSS probability and percentile for supplied CVEs. Process up to 500 unique entries from batchOffset; response byte limits can return fewer whole entries. Resume with nextBatchOffset as batchOffset, the original cves and returned score date as date. deferredCves were not queried; withheldCves were processed but omitted, and either list can be a declared preview. Missing scores remain unknown; use epss_list_reference for coverage and interpretation.

NameTypeReqDescription
batchOffsetinteger–Resume in first-occurrence normalized unique input order; resubmit the original cves, returned score date and original policy/severity inputs.
cvesarrayyesOne to 5000 CVE identifiers; whitespace, comma or semicolon-delimited strings are also accepted.
datestring–UTC date YYYY-MM-DD from 2021-04-14 through today; omitted or blank selects latest available data.
NameTypeReqDescription
batchOffsetinteger–Starting offset in the original normalized unique input.
budgetLimitedboolean–True when whole entries or accounting lists were shortened to fit the serialized response budget.
deferredCountinteger–Identifiers beyond this call workload cap, not queried.
deferredCvesarray–Never-queried identifiers beyond this call workload cap; complete unless deferredCvesComplete is false. Resume using nextBatchOffset and the original submission.
deferredCvesCompleteboolean–True when deferredCves includes every never-queried deferred identifier.
duplicateCountinteger–Duplicate submitted entries removed.
errorobject–Present when the call failed. Absent on success.
nextBatchOffsetinteger–Resume with this batchOffset and the original cves, returned date and original severity/policy inputs.
noticestring–Missing-data, deferred-work or model-metadata caveats.
processedCountinteger–Unique identifiers processed, including invalid formats.
provenanceobject–Source and model attribution.
requestedCountinteger–Unique normalized identifiers submitted.
returnedCountinteger–Processed identifiers whose complete score, history or unscored entry is included.
scoresarray–Forecasts ordered by EPSS descending then CVE.
unscoredCvesarray–Retained processed identifiers without scores, in request order.
withheldCountinteger–Processed identifiers withheld by the response byte budget; queried valid entries are included in processedCount.
withheldCvesarray–Already processed identifiers withheld by the byte budget, in original input order; may be a preview.
withheldCvesCompleteboolean–True when withheldCves includes every withheld identifier.

No examples provided.

epss_get_timeseries ~226

Retrieve an EPSS anchor and up to 30 preceding daily observations for up to 50 unique CVEs from batchOffset. Response byte limits retain whole history items. Resume CVE batches with nextBatchOffset as batchOffset, the original cves and returned score date as date; withheldCves were processed, deferredCves were not queried, and lists can be declared previews. Exact 7-day and 30-day deltas require their calendar baselines; gaps remain unknown. Model boundaries do not explain score movement. Re-anchor using previousAnchorDate for the preceding history window; that snapshot may be unavailable.

NameTypeReqDescription
batchOffsetinteger–Resume in first-occurrence normalized unique input order; resubmit the original cves, returned score date and original policy/severity inputs.
cvesarrayyesOne to 5000 CVE identifiers; whitespace, comma or semicolon-delimited strings are also accepted.
datestring–UTC date YYYY-MM-DD from 2021-04-14 through today; omitted or blank selects latest available data.
NameTypeReqDescription
batchOffsetinteger–Starting offset in the original normalized unique input.
budgetLimitedboolean–True when whole entries or accounting lists were shortened to fit the serialized response budget.
deferredCountinteger–Identifiers beyond this call workload cap, not queried.
deferredCvesarray–Never-queried identifiers beyond this call workload cap; complete unless deferredCvesComplete is false. Resume using nextBatchOffset and the original submission.
deferredCvesCompleteboolean–True when deferredCves includes every never-queried deferred identifier.
duplicateCountinteger–Duplicate submitted entries removed.
errorobject–Present when the call failed. Absent on success.
itemsarray–Derived trajectories ordered by anchor EPSS descending then CVE.
nextBatchOffsetinteger–Resume with this batchOffset and the original cves, returned date and original severity/policy inputs.
noticestring–Missing-data, deferred-work or model-metadata caveats.
processedCountinteger–Unique identifiers processed, including invalid formats.
provenanceobject–Source and model attribution.
requestedCountinteger–Unique normalized identifiers submitted.
returnedCountinteger–Processed identifiers whose complete score, history or unscored entry is included.
unscoredCvesarray–Retained processed identifiers without scores, in request order.
withheldCountinteger–Processed identifiers withheld by the response byte budget; queried valid entries are included in processedCount.
withheldCvesarray–Already processed identifiers withheld by the byte budget, in original input order; may be a preview.
withheldCvesCompleteboolean–True when withheldCves includes every withheld identifier.

No examples provided.

epss_list_reference ~79

Explain FIRST EPSS interpretation, model publishing dates, lookup coverage and transparent prioritization policy. Use this static reference before interpreting missing scores, score movement or probability versus percentile thresholds.

NameTypeReqDescription
topicstring–interpretation: score meaning; models: publishing history; coverage: limits and missing data; prioritization: tier policy; all: every topic.
NameTypeReqDescription
errorobject–Present when the call failed. Absent on success.
topicsarray–Selected reference topics.
verifiedAtstring–Primary-source verification date.

No examples provided.

epss_prioritize_cves ~279

Assign remediation tiers using latest or dated EPSS and caller-supplied CVSS base severity. Defaults are severity >= 7 and EPSS probability >= 0.10; select percentile explicitly for population rank. Missing severity stays in epssOnly and missing EPSS stays unscored. Thresholds are policy conventions, not FIRST guidance. Process up to 500 unique entries from batchOffset, returning whole entries within the byte budget. Resume using nextBatchOffset as batchOffset, the original cves with original cvssBaseScore values, returned score date as date, and the same severityThreshold and likelihood. Deferred lists may be declared previews; withheldCves were already processed.

NameTypeReqDescription
batchOffsetinteger–Resume in first-occurrence normalized unique input order; resubmit the original cves, returned score date and original policy/severity inputs.
cvesarrayyesOne to 5000 CVEs with optional caller severity; process up to 500 unique identifiers from batchOffset.
datestring–UTC date YYYY-MM-DD from 2021-04-14 through today; omitted or blank selects latest available data.
likelihood––Select one likelihood metric and threshold; omitted uses EPSS >= 0.10.
severityThresholdnumber–Inclusive high severity threshold, default 7.
NameTypeReqDescription
batchOffsetinteger–Starting offset in the original normalized unique input.
budgetLimitedboolean–True when whole entries or accounting lists were shortened to fit the serialized response budget.
deferredCountinteger–Identifiers beyond this call workload cap, not queried.
deferredCvesarray–Never-queried identifiers beyond this call workload cap; complete unless deferredCvesComplete is false. Resume using nextBatchOffset and the original submission.
deferredCvesCompleteboolean–True when deferredCves includes every never-queried deferred identifier.
duplicateCountinteger–Duplicate submitted entries removed.
epssOnlyarray–Scored CVEs without caller severity; never classified as low severity.
errorobject–Present when the call failed. Absent on success.
nextBatchOffsetinteger–Resume with this batchOffset and the original cves, returned date and original severity/policy inputs.
noticestring–Missing-data, deferred-work or model-metadata caveats.
processedCountinteger–Unique identifiers processed, including invalid formats.
provenanceobject–Source and model attribution.
requestedCountinteger–Unique normalized identifiers submitted.
returnedCountinteger–Processed identifiers whose complete score, history or unscored entry is included.
thresholdsobject–Applied policy conventions, not FIRST recommendations.
tiersobject–Policy tiers, each sorted by EPSS, CVSS descending then CVE ascending.
unscoredCvesarray–Processed identifiers without EPSS, preserving supplied severity.
withheldCountinteger–Processed identifiers withheld by the response byte budget; queried valid entries are included in processedCount.
withheldCvesarray–Already processed identifiers withheld by the byte budget, in original input order; may be a preview.
withheldCvesCompleteboolean–True when withheldCves includes every withheld identifier.

No examples provided.

epss_query_threshold ~326

Discover CVEs using inclusive EPSS or percentile bounds, CVE year or dataset-addition recency; filters intersect and at least one is required. Examine one candidate page in the upstream FIRST order, which is not ranked by EPSS, so the first page does not hold the highest scores. Each serialized response surface fits 65536 UTF-8 bytes; budgetLimited and withheldCount disclose whole matches withheld, with nextOffset at the first withheld match. Year filtering can return an empty page with nextOffset; candidateTotal is a broad-query total, not an exact-year total. Continue with the same filters, limit, returned score date and nextOffset.

NameTypeReqDescription
addedWithinDaysinteger–Dataset-addition recency relative to upstream present, independent of historical date.
datestring–UTC date YYYY-MM-DD from 2021-04-14 through today; omitted or blank selects latest available data.
limitinteger–Requested candidates per page; positive safe integers above 10000 are clamped to 10000 before exact-year filtering.
maxEpssnumber–Inclusive maximum EPSS probability.
maxPercentilenumber–Inclusive maximum population percentile rank.
minEpssnumber–Inclusive minimum EPSS probability.
minPercentilenumber–Inclusive minimum population percentile rank.
offsetinteger–Candidate-space offset; use returned nextOffset for continuation.
yearinteger–Exact CVE year from 1999 through the current UTC year; candidate pages may contain no matches.
NameTypeReqDescription
errorobject–Present when the call failed. Absent on success.
filtersobject–Applied filters; combine with provenance scoreDates to pin continuation.
noticestring–Missing-data, deferred-work or model-metadata caveats.
paginationobject–Candidate pagination accounting.
provenanceobject–Snapshot source and model metadata, including dates from filtered-out candidates.
scoresarray–Retained records from this candidate page.

No examples provided.

Install

How do I install the io.github.cyanheads/first-epss-mcp-server server?

io.github.cyanheads/first-epss-mcp-server is a hosted endpoint at https://first-epss.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 · first-epss.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-first-epss-mcp-server 'https://first-epss.caseyjhand.com/mcp'
Common questions

What is the io.github.cyanheads/first-epss-mcp-server server?

io.github.cyanheads/first-epss-mcp-server is listed in the public MCP registry as io.github.cyanheads/first-epss-mcp-server. Look up FIRST EPSS scores and daily history, find CVEs by threshold, and prioritize them with CVSS. This page covers its hosted endpoint (https://first-epss.caseyjhand.com/mcp).

Is the io.github.cyanheads/first-epss-mcp-server server safe to use?

io.github.cyanheads/first-epss-mcp-server scores 80 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/first-epss-mcp-server server expose?

io.github.cyanheads/first-epss-mcp-server exposes 5 tools: epss_get_scores, epss_get_timeseries, epss_query_threshold, epss_prioritize_cves, epss_list_reference. Their descriptions and schemas cost roughly 1,109 tokens of context every time the server is loaded.

Does the io.github.cyanheads/first-epss-mcp-server server require authentication?

No. We connected to io.github.cyanheads/first-epss-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.cyanheads/first-epss-mcp-server server still maintained?

io.github.cyanheads/first-epss-mcp-server 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.