io.github.Ooak21/cortex402
NPM · CORTEX402-MCP
Pay-per-call x402 data products on Base mainnet — sanctions, aviation weather, US property.
Available components
Last scanned (23 hours ago)
Scores higher than 2% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security79
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 400 of 557 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 153 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
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.
- 30 Oct 26 0
- CVE-2026-118664 affects this package: high ▼ security
- 24 Oct 26 −2
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
- 12 Oct 26 −1
- CVE-2026-45822 affects this package: high ▼ security
- CVE-2026-48779 affects this package: high ▼ security
- CVE-2026-45736 affects this package: high ▼ security
- 6 Oct 26 +1
- CVE-2026-45736 no longer affects this package ▲ security
- CVE-2026-45822 no longer affects this package ▲ security
- CVE-2026-48779 no longer affects this package ▲ security
- 28 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
- 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
- 15 Sept 26 0
- CVE-2026-67316 no longer affects this package ▲ security
- CVE-2026-67313 no longer affects this package ▲ security
- CVE-2026-67312 no longer affects this package ▲ security
- CVE-2026-67321 no longer affects this package ▲ security
- CVE-2026-67315 no longer affects this package ▲ security
- CVE-2026-67320 no longer affects this package ▲ security
- CVE-2026-67317 no longer affects this package ▲ security
- CVE-2026-67318 no longer affects this package ▲ security
- CVE-2026-67319 no longer affects this package ▲ security
- CVE-2026-67314 no longer affects this package ▲ security
- 1 Sept 26 0
- CVE-2026-45822 affects this package: high ▼ security
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 4 Nov 2026 · Analysed npm/cortex402-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-qr28-fpjm-wq7f | CVE-2026-118664 | high | yes | |
| GHSA-vcc3-ghjq-m6fr | CVE-2026-45822 | medium | yes | |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-58qx-3vcg-4xpx | CVE-2026-45736 | medium | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-96hv-2xvq-fx4p | CVE-2026-48779 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 400 packages
| Packages resolved | 400 |
|---|---|
| Deprecated | 13 |
| Stale | 104 |
| No linked repository | 2 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the io.github.Ooak21/cortex402 MCP server?
io.github.Ooak21/cortex402 runs locally as an npm package, launched with npx -y cortex402-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · cortex402-mcp
claude mcp add ooak21-cortex402 -- npx -y cortex402-mcp
What is the io.github.Ooak21/cortex402 MCP server?
io.github.Ooak21/cortex402 is an MCP server listed in the public MCP registry as io.github.Ooak21/cortex402. Pay-per-call x402 data products on Base mainnet, sanctions, aviation weather, US property. This page covers its npm package (cortex402-mcp).
Is the io.github.Ooak21/cortex402 MCP server safe to use?
io.github.Ooak21/cortex402 scores 28 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 4 November 2026. It declares no install or post-install scripts. 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.
Is the io.github.Ooak21/cortex402 MCP server still maintained?
io.github.Ooak21/cortex402 is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Ooak21/cortex402 MCP server under?
io.github.Ooak21/cortex402 declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.