io.github.kcw2034-sayouzone/mcp-opendart-server
PYPI · SAYOU-OPENDART-MCP
An MCP server that provides OpenDart API
Available components
Last scanned (1 hour ago)
Scores higher than 0% of PyPI servers
Category Finance and Payments
Recent critical change
CVE-2026-32871 affects this package (4 Aug 2026). See the changelog before you install this server.
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 Security75
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 3 of 91 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency31
- 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
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 246 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks 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 we can run it. 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.
- 5 Nov 26 0
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 0
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 0
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 0
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 0
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 0
- Malware scan: pass → unverified ▼ security
- 13 Oct 26 −25
- Known CVEs: unverified → fail ▼ critical
- Score status: scored → failed ▼ critical
- Dependency health: unverified → 0.98 ▲ functional
- 12 Oct 26 +25
- Known CVEs: fail → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: partial → unverified ▼ functional
- Score status: failed → scored ▲ 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 5 Nov 2026 · Analysed pypi/sayou-opendart-mcp@0.0.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 16 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-5h2m-4q8j-pqpj | CVE-2025-69196 | high | yes | |
| GHSA-c2jp-c369-7pvx | high | yes | ||
| GHSA-m8x7-r2rg-vh5g | CVE-2025-64340 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H | yes |
| GHSA-mxxr-jv3v-6pgc | CVE-2025-62800 | medium | yes | |
| GHSA-rcfx-77hg-w2wv | high | yes | ||
| GHSA-rj5c-58rq-j5g5 | CVE-2025-62801 | medium | yes | |
| GHSA-rww4-4w9c-7733 | CVE-2026-27124 | high | yes | |
| GHSA-vv7q-7jx5-f767 | CVE-2026-32871 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | yes |
| PYSEC-2026-1364 | CVE-2025-62800 | none | yes | |
| PYSEC-2026-1365 | CVE-2025-62801 | none | yes | |
| PYSEC-2026-2474 | CVE-2025-69196 | none | yes | |
| PYSEC-2026-2475 | CVE-2025-64340 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H | yes |
| PYSEC-2026-2476 | CVE-2026-27124 | none | yes | |
| PYSEC-2026-338 | CVE-2026-32871 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | yes |
| GHSA-vfmq-68hx-4jfw | CVE-2026-41066 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| PYSEC-2026-87 | CVE-2026-41066 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 91 packages
| Packages resolved | 91 |
|---|---|
| Stale | 3 |
| 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. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.
How do I install the io.github.kcw2034-sayouzone/mcp-opendart-server server?
io.github.kcw2034-sayouzone/mcp-opendart-server runs locally as a PyPI package, launched with uvx sayou-opendart-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · sayou-opendart-mcp
claude mcp add kcw2034-sayouzone-mcp-opendart-server -- uvx sayou-opendart-mcp