P0: CVE, package and domain checks
REMOTE · X402-BAZAAR-RANK.X402-BAZAAR-RANK-WORKER.WORKERS.DEV
CVE with EPSS and CISA KEV, package risk, software EOL, domain and IP reports, pay per call
Available components
Last scanned (16 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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 Security63
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2046 tokens (~227/item across 9 items; 9 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 Management47
- Stability observed for 14 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 0
- Tool “domain_report_batch” rewrote its description, which is the text the model reads security
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 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.
- 13 Nov 26 +1
- Tool “check_infra” rewrote its description, which is the text the model reads security
- Tool “domain_report” rewrote its description, which is the text the model reads security
- Tool “domain_report_batch” rewrote its description, which is the text the model reads security
- Tool “ip_passport” rewrote its description, which is the text the model reads security
- Tool “package_risk” rewrote its description, which is the text the model reads security
- Tool “site_snapshot” rewrote its description, which is the text the model reads security
- Tool “software_eol” rewrote its description, which is the text the model reads security
- Tool “vuln_cve” rewrote its description, which is the text the model reads security
- Tool “vuln_kev_new” rewrote its description, which is the text the model reads security
- Schema quality: 290 → 229 ▲ functional
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 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.
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 21 Nov 2026 · Probed https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/cve-package-domain-security
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=x402-bazaar-rank-worker.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 8 Nov 2026 | 6 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6c09b073fe5d3fd83fd987465725765b6e5 |
| SANs: *.x402-bazaar-rank-worker.workers.dev, x402-bazaar-rank-worker.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/cve-package-domain-security | Verified | 200 | |
| http (plaintext) | http://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/cve-package-domain-security | Served over HTTP | 200 |
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 →
check_infra Check infra ~312
Use when you need to check infrastructure in one call: any combination (at least one) of ip (ASN, Tor exit, cloud range), domain (status, TLS, robots), cve (CVSS, EPSS, CISA KEV). Returns the paid x402 request for your input (GET /check/infra, $0.015 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For one input use ip_passport, vuln_cve, package_risk or software_eol; for DNS, SPF, DMARC and registration use domain_report; for sitemap or WordPress use site_snapshot. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| cve | string | – | CVE id, e.g. CVE-2021-44228 |
| domain | string | – | Host name of your site, e.g. example.com |
| ip | string | – | Public IPv4 or IPv6 address. At least one of ip, domain, cve, package, software is required |
| package | string | – | ecosystem:name@version, e.g. npm:lodash@4.17.15 (npm, PyPI, Go, crates.io, RubyGems, Maven, NuGet) |
| software | string | – | product@version, e.g. python@3.8.10 (endoflife.date slug) |
No output schema declared.
No examples provided.
domain_report Domain report ~179
Use when you need one report on a domain: DNS records (A, AAAA, MX, NS, TXT, CAA) with SPF and DMARC parsed, RDAP registration for .com, .net and .org (registrar, dates, status, nameservers, DNSSEC). Returns the paid x402 request for your input (GET /domain/report, $0.005 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For several domains use domain_report_batch. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | domain name, e.g. example.com (a URL is accepted; only its host is used). IP addresses and private or local names are refused |
No output schema declared.
No examples provided.
domain_report_batch Domain report batch ~124
Use when you need to vet several domains at once (vendors, leads, lookalikes): up to 10 domains in one POST, each answered exactly like /domain/report. Returns the paid x402 request for your input (POST /domain/report/batch, $0.05 per call; schema linked). POST that JSON body to the URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For one domain use domain_report.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | 1 to 10 domains; duplicates are removed |
No output schema declared.
No examples provided.
ip_passport IP passport ~197
Use when you need to profile an IP address in one call: ASN, AS name and country of its announced range, whether it is a current Tor exit node, and whether it lies in a public cloud range. Returns the paid x402 request for your input (GET /ip/passport, $0.003 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. One public IP only (private and reserved addresses are refused before any charge); to check it together with a domain, CVE, package or software version in one call use check_infra. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | Public IPv4 or IPv6 address, e.g. 1.1.1.1 or 2606:4700:4700::1111 |
No output schema declared.
No examples provided.
package_risk Package risk ~196
Use when you need to vet a dependency before installing or shipping it: pass ecosystem (npm, PyPI, Go, crates.io, RubyGems, Maven, NuGet). Returns the paid x402 request for your input (GET /package/risk, $0.005 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. One exact package version. For a single CVE id use vuln_cve; to know whether a product or runtime version is still supported use software_eol. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem |
| name | string | yes | Package name; Maven is groupId:artifactId, Go is the module path |
| version | string | yes | Exact version, e.g. 4.17.15 |
No output schema declared.
No examples provided.
site_snapshot Site snapshot ~170
Use when you need a health and content snapshot of your own website: HTTP status, final URL, TLS, server, robots.txt and sitemap, plus WordPress REST. Returns the paid x402 request for your input (GET /site/snapshot, $0.005 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For DNS, SPF, DMARC and registration use domain_report; to check a site together with an IP, CVE or package use check_infra. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Root of your own https site, e.g. https://example.com/ (host name only, no path) |
No output schema declared.
No examples provided.
software_eol Software eol ~207
Use when you need to know if a software version is still supported: pass product (python, nodejs, ubuntu, postgresql, ...) and version (3.8.10) for its release cycle, end-of-life date. Returns the paid x402 request for your input (GET /software/eol, $0.002 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Support and end-of-life status only; for known vulnerabilities of a package version use package_risk, of a CVE id use vuln_cve. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | endoflife.date product slug, e.g. python, nodejs, ubuntu |
| version | string | – | Version, e.g. 3.8.10 or 22.04; omit to list the newest cycles |
No output schema declared.
No examples provided.
vuln_cve Vuln cve ~189
Use when you need to triage a CVE: description, CVSS per publisher, dates, CWE, key references, affected products, CISA SSVC, FIRST EPSS with a 30-day series and CISA KEV status in one call. Returns the paid x402 request for your input (GET /vuln/cve, $0.005 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. One CVE id. For CVEs newly added to CISA KEV since a date use vuln_kev_new; for the vulnerabilities of a package version use package_risk. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | CVE identifier, e.g. CVE-2021-44228 |
No output schema declared.
No examples provided.
vuln_kev_new Vuln kev new ~268
Use when you track exploited vulnerabilities: CVEs CISA added to its Known Exploited Vulnerabilities catalog since a date (since=YYYY-MM-DD), newest first, with date added, due date, vendor, product. Returns the paid x402 request for your input (GET /vuln/kev/new, $0.003 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. KEV additions since a date, newest first (limit up to 200), not a lookup; for CVSS, EPSS and KEV status of one CVE use vuln_cve. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string|integer | – | Max entries returned, 1..200 (default 50) |
| product | string | – | Optional: product contains this text (case-insensitive) |
| ransomware | string | – | Optional: CISA knownRansomwareCampaignUse value |
| since | string | yes | Only entries added on/after this date, YYYY-MM-DD (not before 2021-11-03) |
| vendor | string | – | Optional: vendor/project contains this text (case-insensitive) |
No output schema declared.
No examples provided.
How do I install the P0: CVE, package and domain checks MCP server?
P0: CVE, package and domain checks is a hosted endpoint at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/cve-package-domain-security, 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 · x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev
claude mcp add --transport http dev-workers-x402-bazaar-rank-worker-x402-bazaar- 'https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/cve-package-domain-security'
What is the P0: CVE, package and domain checks MCP server?
P0: CVE, package and domain checks is an MCP server listed in the public MCP registry as dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/cve-pa…. CVE with EPSS and CISA KEV, package risk, software EOL, domain and IP reports, pay per call. This page covers its hosted endpoint (https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/cve-package-domain-security).
Is the P0: CVE, package and domain checks MCP server safe to use?
P0: CVE, package and domain checks scores 70 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 P0: CVE, package and domain checks MCP server expose?
P0: CVE, package and domain checks exposes 9 tools: vuln_cve, vuln_kev_new, package_risk, software_eol, domain_report, and 4 more. Their descriptions and schemas cost roughly 1,842 tokens of context every time the server is loaded.
Does the P0: CVE, package and domain checks MCP server require authentication?
No. We connected to P0: CVE, package and domain checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the P0: CVE, package and domain checks MCP server still maintained?
P0: CVE, package and domain checks is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the P0: CVE, package and domain checks MCP server?
VerifyMCP ran 13 checks on P0: CVE, package and domain checks, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.