io.github.daredoole/audio-calibration-mcp
version 0.2.0-beta.1
- scanned 2026-10-16
- source github.com/daredoole/audio-calibration-mcp
- commit 02a7ce118b65
- transport stdio
- files read 29
- methodology 0.2.0
- ruleset 0.1.1
87
1 vendored or minified path was excluded before scanning; machine-generated bundles are not the server's own code
100measured on 65% of this axis
47
88measured on 65% of this axis
65
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.
Code Safety
- lib/listening-spatial.mjs:22mcp-js-prototype-pollution-merge-loop (medium/medium)
Keys from a caller-supplied object are copied onto a target without excluding __proto__ / constructor / prototype. A tool argument carrying __proto__ then mutates Object.prototype for the whole process, which can turn an unrelated later property read into attacker-controlled data.
for (const systemId of systems) { const rows = responses.filter(response => response.systemId === systemId), scores = rows.map(row => Number(row.score)).filter(Number.isFinite); bySystem[systemId] = { observations: scores.length, mean: mean(scores), standardDeviation: Math.sqrt(variance(scores)), confidenceInterval95: scores.length ? [mean(scores) - 1.96 * Math.sqrt(variance(scores) / scores.length), mean(scores) + 1.96 * Math.sqrt(variance(scores) / scores.length)] : null }; } const screening = responses.filter(response => typeof response.correct === "boolean"), successes = screening.filter(response => response.correct).length; - lib/measurement-science.mjs:152mcp-js-prototype-pollution-merge-loop (medium/medium)
Keys from a caller-supplied object are copied onto a target without excluding __proto__ / constructor / prototype. A tool argument carrying __proto__ then mutates Object.prototype for the whole process, which can turn an unrelated later property read into attacker-controlled data.
if (!Array.isArray(metrics) || metrics.length < 2) throw new Error("At least two positions are required"); const fields = ["clarityC50Db", "clarityC80Db", "definitionD50Percent", "centerTimeMs"], summary = {}; for (const field of fields) { const values = metrics.map(item => finite(item[field], field)); summary[field] = { mean: mean(values), standardDeviation: Math.sqrt(variance(values)), minimum: Math.min(...values), maximum: Math.max(...values) }; } return { positions: metrics.length, spatialVariance: summary, claimLevel: "ISO-3382-aligned screening" }; } - scripts/rew-state.mjs:4mcp-js-prototype-pollution-merge-loop (medium/medium)
Keys from a caller-supplied object are copied onto a target without excluding __proto__ / constructor / prototype. A tool argument carrying __proto__ then mutates Object.prototype for the whole process, which can turn an unrelated later property read into attacker-controlled data.
const paths = ["/measure/commands", "/measure/command", "/measure/status", "/measure/timing/reference", "/measure/sequential-channels", "/measure/sweep/repetitions", "/measure/sweep/configuration", "/measure/level", "/measure/protection-options", "/application/blocking"]; const state = {}; for (const path of paths) { try { state[path] = await rew(path); } catch (error) { state[path] = { error: error.message }; } } console.log(JSON.stringify(state, null, 2)); - scripts/rew-state.mjs:4mcp-js-prototype-pollution-merge-loop (medium/medium)
Keys from a caller-supplied object are copied onto a target without excluding __proto__ / constructor / prototype. A tool argument carrying __proto__ then mutates Object.prototype for the whole process, which can turn an unrelated later property read into attacker-controlled data.
const paths = ["/measure/commands", "/measure/command", "/measure/status", "/measure/timing/reference", "/measure/sequential-channels", "/measure/sweep/repetitions", "/measure/sweep/configuration", "/measure/level", "/measure/protection-options", "/application/blocking"]; const state = {}; for (const path of paths) { try { state[path] = await rew(path); } catch (error) { state[path] = { error: error.message }; } } console.log(JSON.stringify(state, null, 2)); - server.mjs:92mcp-js-prototype-pollution-merge-loop (medium/medium)
Keys from a caller-supplied object are copied onto a target without excluding __proto__ / constructor / prototype. A tool argument carrying __proto__ then mutates Object.prototype for the whole process, which can turn an unrelated later property read into attacker-controlled data.
for (const name of ["profiles", "sessions", "measurements", "backups", "reports", "filters", "support", "datasets"]) { const dir = join(root, name); await mkdir(dir, { recursive: true }); groups[name] = (await readdir(dir, { withFileTypes: true })).filter(x => x.isFile()).map(x => x.name).slice(0, 200); } return ok({ root, groups });
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
detect-secrets matched 8 credential-shaped string(s), every one from a keyword or entropy heuristic (Base64 High Entropy String, Hex High Entropy String). Those flag placeholders, variable names and content hashes as readily as credentials, so they do not establish the committed credential `03` §4's 0 asserts, and this sub-check is not scored; Base64 High Entropy String at dist/cli.cjs:14482; Base64 High Entropy String at dist/server.mjs:27829; Hex High Entropy String at fixtures/reference/catalog.json:34; Hex High Entropy String at fixtures/reference/catalog.json:64; Hex High Entropy String at fixtures/reference/catalog.json:93; Hex High Entropy String at fixtures/reference/catalog.json:125; Hex High Entropy String at fixtures/reference/manifest.json:7; Hex High Entropy String at server.json:15
- authorization_granularity
104 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
- package-lock.jsonproxy-addr 2.0.7 — GHSA-jqcg-44mw-7w3h
transitive, CVSS 9.1, fixed in 2.0.8
https://osv.dev/vulnerability/GHSA-jqcg-44mw-7w3h - package-lock.json@modelcontextprotocol/sdk 1.30.0 — GHSA-6qxp-vccf-f47h
direct, CVSS 7.5, fixed in 1.31.0
https://osv.dev/vulnerability/GHSA-6qxp-vccf-f47h - package-lock.jsonbrace-expansion 5.0.9 — GHSA-6j4f-fj2g-mc7p
transitive, CVSS 7.5, fixed in 5.0.10
https://osv.dev/vulnerability/GHSA-6j4f-fj2g-mc7p - package-lock.jsonbrace-expansion 5.0.9 — GHSA-qhr7-859c-m2p7
transitive, CVSS 7.5, fixed in 5.0.11
https://osv.dev/vulnerability/GHSA-qhr7-859c-m2p7 - package-lock.jsonfast-uri 3.1.6 — GHSA-58mr-gqgx-xq4g
transitive, CVSS 7.5, fixed in 3.1.7
https://osv.dev/vulnerability/GHSA-58mr-gqgx-xq4g - package-lock.jsonfast-uri 3.1.6 — GHSA-qw65-cvwx-89v3
transitive, CVSS 7.5, fixed in 3.1.7
https://osv.dev/vulnerability/GHSA-qw65-cvwx-89v3 - package-lock.jsonip-address 10.5.0 — GHSA-2vr4-cq9g-pvrc
transitive, CVSS 6.9, fixed in 10.5.1
https://osv.dev/vulnerability/GHSA-2vr4-cq9g-pvrc - package-lock.jsonhono 4.13.4 — GHSA-gqvv-2mrq-wpjv
transitive, CVSS 6.5, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-gqvv-2mrq-wpjv - package-lock.jsonip-address 10.5.0 — GHSA-h3mg-xc3c-68pw
transitive, CVSS 6.3, fixed in 10.7.1
https://osv.dev/vulnerability/GHSA-h3mg-xc3c-68pw - package-lock.jsonip-address 10.5.0 — GHSA-j6r3-76f7-8jcv
transitive, CVSS 6.3, fixed in 10.7.1
https://osv.dev/vulnerability/GHSA-j6r3-76f7-8jcv - package-lock.jsonip-address 10.5.0 — GHSA-rpw4-54j3-4h4q
transitive, CVSS 6.3, fixed in 10.5.1
https://osv.dev/vulnerability/GHSA-rpw4-54j3-4h4q - package-lock.jsonqs 6.15.3 — GHSA-4mjr-xmp4-gh2g
transitive, CVSS 6.3, fixed in 6.16.0
https://osv.dev/vulnerability/GHSA-4mjr-xmp4-gh2g - package-lock.jsonqs 6.15.3 — GHSA-x5fp-wj9c-mxmx
transitive, CVSS 6.3, fixed in 6.16.0
https://osv.dev/vulnerability/GHSA-x5fp-wj9c-mxmx - package-lock.jsonhono 4.13.4 — GHSA-crvj-82cr-hjcx
transitive, CVSS 5.9, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-crvj-82cr-hjcx - package-lock.jsonbrace-expansion 5.0.9 — GHSA-q2hr-2g5m-vwhr
transitive, CVSS 5.3, fixed in 5.0.12
https://osv.dev/vulnerability/GHSA-q2hr-2g5m-vwhr - package-lock.jsonhono 4.13.4 — GHSA-g6gw-c38x-mqfc
transitive, CVSS 5.3, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-g6gw-c38x-mqfc - package-lock.jsonfast-uri 3.1.6 — GHSA-hrr3-gc8f-f4qj
transitive, CVSS 4.8, fixed in 3.1.8
https://osv.dev/vulnerability/GHSA-hrr3-gc8f-f4qj - package-lock.jsonhono 4.13.4 — GHSA-hxh3-vqpv-xpqv
transitive, CVSS 4.7, fixed in 4.13.7
https://osv.dev/vulnerability/GHSA-hxh3-vqpv-xpqv
Maintenance
- recency
last commit 28 day(s) before 2026-10-16
- issue_responsiveness
this repository has no issues `03` §5's window covers. An unanswered issue scores 0 under §5, but a repository with no issues filed has not failed to answer one.
- release_cadence
median release gap 1 days (by releases), last release 49 day(s) ago
- 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), 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
SECURITY.md present
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.