io.github.stuchapin909/open-eagle-eye
NPM · OPENEAGLEEYE
Live snapshots from ~29,000 public cameras across 11 countries — traffic, weather, webcams
Available components
Last scanned (23 hours ago)
Scores higher than 9% of npm servers
Category Maps and Location
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.28.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 34 of 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 234 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, 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 →
Checks we ran (9)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
Checks we could not complete (5)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.
- Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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 0
- CVE-2026-44487 affects this package: high ▼ security
- CVE-2026-42264 affects this package: high ▼ security
- CVE-2026-67317 affects this package: high ▼ security
- CVE-2026-101902 affects this package: high ▼ security
- CVE-2026-42033 affects this package: high ▼ security
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-42044 affects this package: high ▼ security
- CVE-2026-42037 affects this package: high ▼ security
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- CVE-2026-67313 affects this package: high ▼ security
- CVE-2026-101904 affects this package: high ▼ security
- CVE-2026-101901 affects this package: high ▼ security
- CVE-2026-42034 affects this package: high ▼ security
- CVE-2026-44488 affects this package: high ▼ security
- CVE-2026-42038 affects this package: high ▼ security
- CVE-2026-44495 affects this package: high ▼ security
- CVE-2026-42043 affects this package: high ▼ security
- CVE-2026-42035 affects this package: high ▼ security
- CVE-2026-42040 affects this package: high ▼ security
- CVE-2026-67318 affects this package: high ▼ security
- CVE-2026-101898 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-42042 affects this package: high ▼ security
- CVE-2026-42039 affects this package: high ▼ security
- CVE-2026-44496 affects this package: high ▼ security
- CVE-2026-67312 affects this package: high ▼ security
- CVE-2026-44490 affects this package: high ▼ security
- CVE-2026-101908 affects this package: high ▼ security
- CVE-2023-54404 affects this package: high ▼ security
- CVE-2026-67316 affects this package: high ▼ security
- CVE-2026-104850 affects this package: high ▼ security
- CVE-2026-42036 affects this package: high ▼ security
- CVE-2025-62718 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- CVE-2026-42041 affects this package: high ▼ security
- CVE-2026-101900 affects this package: high ▼ security
- CVE-2026-40175 affects this package: high ▼ security
- CVE-2026-44494 affects this package: high ▼ security
- CVE-2026-118663 affects this package: high ▼ security
- CVE-2026-67319 affects this package: high ▼ security
- CVE-2026-44486 affects this package: high ▼ security
- 20 Nov 26 0
- CVE-2026-44487 affects this package: high ▼ security
- CVE-2026-42264 affects this package: high ▼ security
- CVE-2026-67317 affects this package: high ▼ security
- CVE-2026-101902 affects this package: high ▼ security
- CVE-2026-42033 affects this package: high ▼ security
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-42044 affects this package: high ▼ security
- CVE-2026-42037 affects this package: high ▼ security
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- CVE-2026-67313 affects this package: high ▼ security
- CVE-2026-101904 affects this package: high ▼ security
- CVE-2026-101901 affects this package: high ▼ security
- CVE-2026-42034 affects this package: high ▼ security
- CVE-2026-44488 affects this package: high ▼ security
- CVE-2026-42038 affects this package: high ▼ security
- CVE-2026-44495 affects this package: high ▼ security
- CVE-2026-42043 affects this package: high ▼ security
- CVE-2026-42035 affects this package: high ▼ security
- CVE-2026-42040 affects this package: high ▼ security
- CVE-2026-67318 affects this package: high ▼ security
- CVE-2026-101898 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-42042 affects this package: high ▼ security
- CVE-2026-42039 affects this package: high ▼ security
- CVE-2026-44496 affects this package: high ▼ security
- CVE-2026-67312 affects this package: high ▼ security
- CVE-2026-44490 affects this package: high ▼ security
- CVE-2026-101908 affects this package: high ▼ security
- CVE-2023-54404 affects this package: high ▼ security
- CVE-2026-67316 affects this package: high ▼ security
- CVE-2026-104850 affects this package: high ▼ security
- CVE-2026-42036 affects this package: high ▼ security
- CVE-2025-62718 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- CVE-2026-42041 affects this package: high ▼ security
- CVE-2026-101900 affects this package: high ▼ security
- CVE-2026-40175 affects this package: high ▼ security
- CVE-2026-44494 affects this package: high ▼ security
- CVE-2026-118663 affects this package: high ▼ security
- CVE-2026-67319 affects this package: high ▼ security
- CVE-2026-44486 affects this package: high ▼ security
- 19 Nov 26 0
- CVE-2026-44487 affects this package: high ▼ security
- CVE-2026-42264 affects this package: high ▼ security
- CVE-2026-67317 affects this package: high ▼ security
- CVE-2026-101902 affects this package: high ▼ security
- CVE-2026-42033 affects this package: high ▼ security
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-42044 affects this package: high ▼ security
- CVE-2026-42037 affects this package: high ▼ security
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- CVE-2026-67313 affects this package: high ▼ security
- CVE-2026-101904 affects this package: high ▼ security
- CVE-2026-101901 affects this package: high ▼ security
- CVE-2026-42034 affects this package: high ▼ security
- CVE-2026-44488 affects this package: high ▼ security
- CVE-2026-42038 affects this package: high ▼ security
- CVE-2026-44495 affects this package: high ▼ security
- CVE-2026-42043 affects this package: high ▼ security
- CVE-2026-42035 affects this package: high ▼ security
- CVE-2026-42040 affects this package: high ▼ security
- CVE-2026-67318 affects this package: high ▼ security
- CVE-2026-101898 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-42042 affects this package: high ▼ security
- CVE-2026-42039 affects this package: high ▼ security
- CVE-2026-44496 affects this package: high ▼ security
- CVE-2026-67312 affects this package: high ▼ security
- CVE-2026-44490 affects this package: high ▼ security
- CVE-2026-101908 affects this package: high ▼ security
- CVE-2023-54404 affects this package: high ▼ security
- CVE-2026-67316 affects this package: high ▼ security
- CVE-2026-104850 affects this package: high ▼ security
- CVE-2026-42036 affects this package: high ▼ security
- CVE-2025-62718 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- CVE-2026-42041 affects this package: high ▼ security
- CVE-2026-101900 affects this package: high ▼ security
- CVE-2026-40175 affects this package: high ▼ security
- CVE-2026-44494 affects this package: high ▼ security
- CVE-2026-118663 affects this package: high ▼ security
- CVE-2026-67319 affects this package: high ▼ security
- CVE-2026-44486 affects this package: high ▼ security
- 18 Nov 26 0
- CVE-2026-44487 affects this package: high ▼ security
- CVE-2026-42264 affects this package: high ▼ security
- CVE-2026-67317 affects this package: high ▼ security
- CVE-2026-101902 affects this package: high ▼ security
- CVE-2026-42033 affects this package: high ▼ security
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-42044 affects this package: high ▼ security
- CVE-2026-42037 affects this package: high ▼ security
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- CVE-2026-67313 affects this package: high ▼ security
- CVE-2026-101904 affects this package: high ▼ security
- CVE-2026-101901 affects this package: high ▼ security
- CVE-2026-42034 affects this package: high ▼ security
- CVE-2026-44488 affects this package: high ▼ security
- CVE-2026-42038 affects this package: high ▼ security
- CVE-2026-44495 affects this package: high ▼ security
- CVE-2026-42043 affects this package: high ▼ security
- CVE-2026-42035 affects this package: high ▼ security
- CVE-2026-42040 affects this package: high ▼ security
- CVE-2026-67318 affects this package: high ▼ security
- CVE-2026-101898 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-42042 affects this package: high ▼ security
- CVE-2026-42039 affects this package: high ▼ security
- CVE-2026-44496 affects this package: high ▼ security
- CVE-2026-67312 affects this package: high ▼ security
- CVE-2026-44490 affects this package: high ▼ security
- CVE-2026-101908 affects this package: high ▼ security
- CVE-2023-54404 affects this package: high ▼ security
- CVE-2026-67316 affects this package: high ▼ security
- CVE-2026-104850 affects this package: high ▼ security
- CVE-2026-42036 affects this package: high ▼ security
- CVE-2025-62718 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- CVE-2026-42041 affects this package: high ▼ security
- CVE-2026-101900 affects this package: high ▼ security
- CVE-2026-40175 affects this package: high ▼ security
- CVE-2026-44494 affects this package: high ▼ security
- CVE-2026-118663 affects this package: high ▼ security
- CVE-2026-67319 affects this package: high ▼ security
- CVE-2026-44486 affects this package: high ▼ security
- 17 Nov 26 0
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- CVE-2026-44487 affects this package: high ▼ security
- CVE-2026-42264 affects this package: high ▼ security
- CVE-2026-67317 affects this package: high ▼ security
- CVE-2026-101902 affects this package: high ▼ security
- CVE-2026-42033 affects this package: high ▼ security
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-42044 affects this package: high ▼ security
- CVE-2026-42037 affects this package: high ▼ security
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- CVE-2026-67313 affects this package: high ▼ security
- CVE-2026-101904 affects this package: high ▼ security
- CVE-2026-101901 affects this package: high ▼ security
- CVE-2026-42034 affects this package: high ▼ security
- CVE-2026-44488 affects this package: high ▼ security
- CVE-2026-42038 affects this package: high ▼ security
- CVE-2026-44495 affects this package: high ▼ security
- CVE-2026-42043 affects this package: high ▼ security
- CVE-2026-42035 affects this package: high ▼ security
- CVE-2026-42040 affects this package: high ▼ security
- CVE-2026-67318 affects this package: high ▼ security
- CVE-2026-101898 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-42042 affects this package: high ▼ security
- CVE-2026-42039 affects this package: high ▼ security
- CVE-2026-44496 affects this package: high ▼ security
- CVE-2026-67312 affects this package: high ▼ security
- CVE-2026-44490 affects this package: high ▼ security
- CVE-2026-101908 affects this package: high ▼ security
- CVE-2023-54404 affects this package: high ▼ security
- CVE-2026-67316 affects this package: high ▼ security
- CVE-2026-104850 affects this package: high ▼ security
- 12 Nov 26 +5
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- 11 Nov 26 −5
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- 23 Oct 26 34
First indexed and scored.
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 · Analysed npm/openeagleeye@8.0.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 42 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-35jp-ww65-95wh | CVE-2026-44494 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N | yes |
| GHSA-3g43-6gmg-66jw | CVE-2026-44495 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-3p68-rc4w-qgx5 | CVE-2025-62718 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-3pq3-5fj3-cg6v | CVE-2026-101898 | high | yes | |
| GHSA-3w6x-2g7m-8v23 | CVE-2026-42044 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N | yes |
| GHSA-42h9-826w-cgv3 | CVE-2026-67313 | medium | yes | |
| GHSA-445q-vr5w-6q77 | CVE-2026-42037 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-4hqw-qxg8-jxx2 | CVE-2026-101900 | medium | yes | |
| GHSA-542g-h47m-68v8 | CVE-2026-101901 | high | yes | |
| GHSA-5c9x-8gcm-mpgx | CVE-2026-42034 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-62hf-57xw-28j9 | CVE-2026-42039 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6chq-wfr3-2hj9 | CVE-2026-42035 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-777c-7fjr-54vf | CVE-2026-44488 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-7q8q-rj6j-mhjq | CVE-2026-67319 | medium | yes | |
| GHSA-898c-q2cr-xwhg | CVE-2026-44490 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L | yes |
| GHSA-9fr6-4gfg-395g | CVE-2026-101902 | medium | yes | |
| GHSA-fvcv-3m26-pcqx | CVE-2026-40175 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-hfxv-24rg-xrqf | CVE-2026-44496 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-j5f8-grm9-p9fc | CVE-2026-44486 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-j8rh-479h-cp32 | CVE-2026-101904 | medium | yes | |
| GHSA-jqh4-m9w3-8hp9 | CVE-2026-67317 | medium | yes | |
| GHSA-m7pr-hjqh-92cm | CVE-2026-42038 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N | yes |
| GHSA-mmx7-hfxf-jppx | CVE-2026-67316 | medium | yes | |
| GHSA-mwf2-3pr3-8698 | CVE-2026-67318 | medium | yes | |
| GHSA-p92q-9vqr-4j8v | CVE-2026-44487 | high | yes | |
| GHSA-pf86-5x62-jrwf | CVE-2026-42033 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-pmv8-rq9r-6j72 | CVE-2026-67312 | medium | yes | |
| GHSA-pmwg-cvhr-8vh7 | CVE-2026-42043 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N | yes |
| GHSA-q8qp-cvcw-x6jj | CVE-2026-42264 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-vf2m-468p-8v99 | CVE-2026-42036 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-vh66-26gq-q6x8 | CVE-2026-101908 | medium | yes | |
| GHSA-w9j2-pvgh-6h63 | CVE-2026-42041 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-xhjh-pmcv-23jw | CVE-2026-42040 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-xx6v-rp6x-q39c | CVE-2026-42042 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N | 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 104 packages
| Packages resolved | 104 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
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.stuchapin909/open-eagle-eye MCP server?
io.github.stuchapin909/open-eagle-eye runs locally as an npm package, launched with npx -y openeagleeye. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · openeagleeye
claude mcp add stuchapin909-open-eagle-eye -- npx -y openeagleeye
What is the io.github.stuchapin909/open-eagle-eye MCP server?
io.github.stuchapin909/open-eagle-eye is an MCP server listed in the public MCP registry as io.github.stuchapin909/open-eagle-eye. Live snapshots from ~29,000 public cameras across 11 countries, traffic, weather, webcams. This page covers its npm package (openeagleeye).
Is the io.github.stuchapin909/open-eagle-eye MCP server safe to use?
io.github.stuchapin909/open-eagle-eye scores 34 out of 100 on VerifyMCP. We recorded 42 known advisories against it as of 21 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.stuchapin909/open-eagle-eye MCP server still maintained?
io.github.stuchapin909/open-eagle-eye 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 licence is the io.github.stuchapin909/open-eagle-eye MCP server under?
io.github.stuchapin909/open-eagle-eye declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.stuchapin909/open-eagle-eye MCP server?
VerifyMCP ran 9 checks on io.github.stuchapin909/open-eagle-eye, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about io.github.stuchapin909/open-eagle-eye: Schema quality, Stability, Tool coverage, Tool safety and 1 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.