io.github.Cifero74/mcp-apple-music
version 1.1.0
- scanned 2026-10-16
- source github.com/Cifero74/mcp-apple-music
- transport stdio
- files read 5
- methodology 0.2.0
- ruleset 0.1.1
100
93measured on 85% of this axis
0
54measured on 70% of this axis
58
The evidence
Every deduction below names the artefact that produced it. Nothing on this page was executed: the source was read, never run, and no running server was contacted.
Auth Posture
- authentication_model
stdio transport: the client launches the server as a subprocess, so the OS process boundary is the auth boundary — `03` §4 does not penalise absent auth here
- transport_security
declared transport: stdio — launched as a subprocess by the client, so the security boundary is the client process, not a network port (`03` §4)
- secret_handling
credentials are read from the environment (APPLE_KEY_ID, APPLE_MUSIC_USER_TOKEN, APPLE_PRIVATE_KEY), but the README does not document which
- authorization_granularity
11 tool registrations and no conditional access logic found — `03` §4 calls this case 'needs human review' and assigns it no score band, so it is not scored here
Dependency Health
- uv.lockcryptography 46.0.5 — PYSEC-2026-36
direct, CVSS 9.8, fixed in 46.0.7
https://osv.dev/vulnerability/PYSEC-2026-36 - uv.lockpyjwt 2.11.0 — PYSEC-2026-4145
direct, CVSS 9.1, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4145 - uv.lockanyio 4.12.1 — PYSEC-2026-4025
transitive, CVSS 9.3, fixed in 4.14.2
https://osv.dev/vulnerability/PYSEC-2026-4025 - uv.lockcryptography 46.0.5 — PYSEC-2026-3553
direct, CVSS 8.7, fixed in 49.0.0
https://osv.dev/vulnerability/PYSEC-2026-3553 - uv.lockcryptography 46.0.5 — PYSEC-2026-3552
direct, CVSS 8.2, fixed in 50.0.0
https://osv.dev/vulnerability/PYSEC-2026-3552 - uv.lockpyjwt 2.11.0 — PYSEC-2026-4183
direct, CVSS 8.2, fixed in 2.15.0
https://osv.dev/vulnerability/PYSEC-2026-4183 - uv.lockmcp 1.26.0 — PYSEC-2026-3481
direct, CVSS 7.6, fixed in 1.27.2
https://osv.dev/vulnerability/PYSEC-2026-3481 - uv.lockmcp 1.26.0 — PYSEC-2026-3483
direct, CVSS 7.6, fixed in 1.28.1
https://osv.dev/vulnerability/PYSEC-2026-3483 - uv.lockcryptography 46.0.5 — GHSA-537c-gmf6-5ccf
direct, CVSS 7.5, fixed in 48.0.1
https://osv.dev/vulnerability/GHSA-537c-gmf6-5ccf - uv.lockmcp 1.26.0 — GHSA-84m7-p3x7-pcfv
direct, CVSS 7.5, fixed in 1.30.0
https://osv.dev/vulnerability/GHSA-84m7-p3x7-pcfv - uv.lockpyjwt 2.11.0 — PYSEC-2026-120
direct, CVSS 7.5, fixed in 2.12.0
https://osv.dev/vulnerability/PYSEC-2026-120 - uv.lockpyjwt 2.11.0 — PYSEC-2026-179
direct, CVSS 7.4, fixed in 2.13.0
https://osv.dev/vulnerability/PYSEC-2026-179 - uv.lockpyjwt 2.11.0 — PYSEC-2026-4144
direct, CVSS 7.4, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4144 - uv.lockpyjwt 2.11.0 — PYSEC-2026-4149
direct, CVSS 7.4, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4149 - uv.lockmcp 1.26.0 — PYSEC-2026-3482
direct, CVSS 7.1, fixed in 1.27.2
https://osv.dev/vulnerability/PYSEC-2026-3482 - uv.lockpython-multipart 0.0.22 — PYSEC-2026-3036
transitive, CVSS 7.5, fixed in 0.0.30
https://osv.dev/vulnerability/PYSEC-2026-3036 - uv.lockpython-multipart 0.0.22 — PYSEC-2026-3039
transitive, CVSS 7.5, fixed in 0.0.27
https://osv.dev/vulnerability/PYSEC-2026-3039 - uv.lockstarlette 0.52.1 — PYSEC-2026-2281
transitive, CVSS 7.5, fixed in 1.1.0
https://osv.dev/vulnerability/PYSEC-2026-2281 - uv.lockstarlette 0.52.1 — PYSEC-2026-249
transitive, CVSS 7.5, fixed in 1.3.1
https://osv.dev/vulnerability/PYSEC-2026-249 - uv.lockcryptography 46.0.5 — PYSEC-2026-3554
direct, CVSS 6.9, fixed in 49.0.0
https://osv.dev/vulnerability/PYSEC-2026-3554 - uv.lockpyjwt 2.11.0 — PYSEC-2026-4146
direct, CVSS 6.5
https://osv.dev/vulnerability/PYSEC-2026-4146 - uv.lockpyjwt 2.11.0 — PYSEC-2026-4152
direct, CVSS 5.9, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4152 - uv.lockpyjwt 2.11.0 — PYSEC-2026-176
direct, CVSS 5.4, fixed in 2.12.1
https://osv.dev/vulnerability/PYSEC-2026-176 - uv.lockcryptography 46.0.5 — PYSEC-2026-35
direct, CVSS 5.3, fixed in 46.0.6
https://osv.dev/vulnerability/PYSEC-2026-35 - uv.lockpyjwt 2.11.0 — PYSEC-2026-178
direct, CVSS 5.3, fixed in 2.13.0
https://osv.dev/vulnerability/PYSEC-2026-178 - uv.lockpyjwt 2.11.0 — PYSEC-2026-4140
direct, CVSS 5.3, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4140 - uv.lockpyjwt 2.11.0 — PYSEC-2026-4141
direct, CVSS 5.3, fixed in 2.15.0
https://osv.dev/vulnerability/PYSEC-2026-4141 - uv.lockpyjwt 2.11.0 — PYSEC-2026-4147
direct, CVSS 4.8, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4147 - uv.lockpyjwt 2.11.0 — PYSEC-2026-4148
direct, CVSS 4.4, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4148 - uv.lockpyjwt 2.11.0 — PYSEC-2026-175
direct, CVSS 4.2, fixed in 2.13.0
https://osv.dev/vulnerability/PYSEC-2026-175 - uv.lockidna 3.11 — PYSEC-2026-215
transitive, CVSS 6.9, fixed in 3.15
https://osv.dev/vulnerability/PYSEC-2026-215 - uv.lockanyio 4.12.1 — PYSEC-2026-4024
transitive, CVSS 6.8, fixed in 4.14.2
https://osv.dev/vulnerability/PYSEC-2026-4024 - uv.lockpython-dotenv 1.2.1 — PYSEC-2026-2270
transitive, CVSS 6.6, fixed in 1.2.2
https://osv.dev/vulnerability/PYSEC-2026-2270 - uv.lockstarlette 0.52.1 — PYSEC-2026-161
transitive, CVSS 6.5, fixed in 1.0.1
https://osv.dev/vulnerability/PYSEC-2026-161 - uv.lockpydantic-settings 2.13.1 — GHSA-4xgf-cpjx-pc3j
transitive, CVSS 5.3, fixed in 2.14.2
https://osv.dev/vulnerability/GHSA-4xgf-cpjx-pc3j - uv.lockpython-multipart 0.0.22 — PYSEC-2026-3038
transitive, CVSS 5.3, fixed in 0.0.26
https://osv.dev/vulnerability/PYSEC-2026-3038 - uv.lockstarlette 0.52.1 — PYSEC-2026-2280
transitive, CVSS 5.3, fixed in 1.1.0
https://osv.dev/vulnerability/PYSEC-2026-2280 - uv.lockstarlette 0.52.1 — PYSEC-2026-248
transitive, CVSS 5.3, fixed in 1.3.0
https://osv.dev/vulnerability/PYSEC-2026-248 - uv.lockpyjwt 2.11.0 — PYSEC-2026-177
direct, CVSS 3.7, fixed in 2.13.0
https://osv.dev/vulnerability/PYSEC-2026-177 - uv.lockpython-multipart 0.0.22 — PYSEC-2026-3037
transitive, CVSS 3.7, fixed in 0.0.30
https://osv.dev/vulnerability/PYSEC-2026-3037 - uv.lockpython-multipart 0.0.22 — PYSEC-2026-3040
transitive, CVSS 3.7, fixed in 0.0.31
https://osv.dev/vulnerability/PYSEC-2026-3040 - uv.lockpython-multipart 0.0.22 — PYSEC-2026-3041
transitive, CVSS 3.7, fixed in 0.0.30
https://osv.dev/vulnerability/PYSEC-2026-3041 - uv.lockpygments 2.19.2 — PYSEC-2026-2987
transitive, CVSS 3.3, fixed in 2.20.0
https://osv.dev/vulnerability/PYSEC-2026-2987
Maintenance
- recency
last commit 7 day(s) before 2026-10-16
- issue_responsiveness
median over 3 issue(s) in the last 6 months: 100.2 day(s) to first maintainer comment
- release_cadence
a release exists but fewer than two fall inside `03` §5's 12-month window, so no median gap can be taken — and §5's remaining bands are all defined on that median. A limit of the methodology, not of this repository.
- bus_factor
sole maintainer
- repository_signals
`03` §5 scores this by quartile WITHIN the server's category, which needs a distribution across every scanned server and so cannot be computed while scanning one. It is a post-pass over the crawl and that pass does not exist yet.
Transparency
- license
LICENSE present with no SPDX-License-Identifier tag; identified as 'MIT' from its text
- readme_quality
README.md: installation instructions (+25), configuration documented (+25), exposed tools or resources enumerated (+30), states what the server does in the first 200 words (+20)
- declared_scopes
neither the README nor the MCP manifest documents what the server accesses or what side effects it has
- changelog
CHANGELOG.md present
- security_contact
no SECURITY.md and no disclosure contact in the README, so a finder has no route to report a vulnerability privately
Contest a finding
Every number here comes from a rule reading published source, and rules get things wrong. If something on this page is incorrect — or correct but mitigated by a check the rule cannot see — open an issue and we answer it in writing. A finding we got wrong is removed and the rule is fixed; one that stands is answered on the record.
Anyone can file: the maintainer, a researcher who disagrees with the classification, or a user who tested the server and could not reproduce it. Name this server and the rule or advisory ID shown beside the finding above. We aim to reply within five business days and to resolve within ten.