io.github.srotzin/hivebank
version 1.0.0
- scanned 2026-10-16
- source github.com/srotzin/hivebank
- commit 8af43d8a5d7b
- transport streamable-http
- files read 56
- methodology 0.2.0
- ruleset 0.1.1
86
61measured on 85% of this axis
35
73measured on 45% of this axis
36
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
- src/routes/echo.js:158mcp-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 allPartyStates = {}; for (const did of parties) { allPartyStates[did] = {}; for (const [key, entry] of currentStates.entries()) { if (entry.state && entry.state.did === did) allPartyStates[did][key] = { state: entry.state, state_hash: entry.state_hash, recorded_at: entry.recorded_at }; - src/middleware/mpp.js:87mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
try { const rpcRes = await fetch(BASE_RPC_URL, { method: 'POST', headers: { 'Content-Type': 'application/json' }, - src/middleware/x402.js:104mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
const usdcLower = USDC_CONTRACT.toLowerCase(); try { const receiptRes = await fetch(BASE_RPC_URL, { method: 'POST', headers: { 'Content-Type': 'application/json' }, - src/routes/settlement.js:21mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
const KEY = require('../lib/internal-key').getInternalKey(); try { await fetch(HIVEBANK_URL + '/v1/bank/rewards/claim', { method: 'POST', headers: { 'Content-Type': 'application/json', 'x-hive-internal': KEY }, - src/server.js:816mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
const ctrl = new AbortController(); const t = setTimeout(() => ctrl.abort(), 15000); await fetch(url, { signal: ctrl.signal }); clearTimeout(t); } catch { - src/services/cross-service.js:9mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
const timeout = setTimeout(() => controller.abort(), timeoutMs); try { const res = await fetch(url, { ...options, signal: controller.signal }); return res; } finally { - src/services/yield-vault.js:148mcp-js-ssrf-nonliteral-url (medium/low)
An outbound request is made to a URL that is not a literal. If any part is caller-supplied the server can be aimed at internal hosts it can reach and the caller cannot.
const ctrl = new AbortController(); const timer = setTimeout(() => ctrl.abort(), 6000); const resp = await fetch(url, { signal: ctrl.signal }); clearTimeout(timer); if (!resp.ok) throw new Error(`HTTP ${resp.status}`);
Auth Posture
- authentication_model
credential enforcement present in source but not documented in the README
- transport_security
declared endpoint(s) are HTTPS: https://hivebank.onrender.com/mcp; scored 80, not 100: `03` §4 reserves 100 for HTTPS *with HSTS*, and an HSTS header can only be seen by connecting, which `04` §9 does not do. This is an unverifiable band, not an observed absence.
- secret_handling
Private Key at src/services/mpc-treasury.js:151; …and 7 more matches
- authorization_granularity
no tool registration was recognised anywhere in the source. An MCP server registers tools by definition, so this is a gap in our detection rather than a server with none, and `03` §4's threshold cannot be applied to it.
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.jsonuuid 10.0.0 — GHSA-w5hq-g745-h8pq
direct, CVSS 7.5, fixed in 11.1.1
https://osv.dev/vulnerability/GHSA-w5hq-g745-h8pq - package-lock.jsonaxios 1.15.1 — GHSA-35jp-ww65-95wh
transitive, CVSS 8.7, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-35jp-ww65-95wh - package-lock.jsonform-data 4.0.5 — GHSA-hmw2-7cc7-3qxx
transitive, CVSS 8.7, fixed in 4.0.6
https://osv.dev/vulnerability/GHSA-hmw2-7cc7-3qxx - package-lock.jsonaxios 1.15.1 — GHSA-pjwm-pj3p-43mv
transitive, CVSS 8.6, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-pjwm-pj3p-43mv - package-lock.jsonaxios 1.15.1 — GHSA-x97p-jq2g-jp4f
transitive, CVSS 8.3, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-x97p-jq2g-jp4f - package-lock.jsonaxios 1.15.1 — GHSA-542g-h47m-68v8
transitive, CVSS 8.2, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-542g-h47m-68v8 - package-lock.jsonaxios 1.15.1 — GHSA-mghh-pgcx-3jjj
transitive, CVSS 8.2, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-mghh-pgcx-3jjj - package-lock.jsonaxios 1.15.1 — GHSA-p92q-9vqr-4j8v
transitive, CVSS 8.2, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-p92q-9vqr-4j8v - package-lock.jsonaxios 1.15.1 — GHSA-777c-7fjr-54vf
transitive, CVSS 7.5, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-777c-7fjr-54vf - package-lock.jsonaxios 1.15.1 — GHSA-hfxv-24rg-xrqf
transitive, CVSS 7.5, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-hfxv-24rg-xrqf - package-lock.jsonaxios 1.15.1 — GHSA-j5f8-grm9-p9fc
transitive, CVSS 7.5, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-j5f8-grm9-p9fc - package-lock.jsonws 8.17.1 — GHSA-96hv-2xvq-fx4p
transitive, CVSS 7.5, fixed in 8.21.0
https://osv.dev/vulnerability/GHSA-96hv-2xvq-fx4p - package-lock.jsonws 8.18.3 — GHSA-96hv-2xvq-fx4p
transitive, CVSS 7.5, fixed in 8.21.0
https://osv.dev/vulnerability/GHSA-96hv-2xvq-fx4p - package-lock.jsonaxios 1.15.1 — GHSA-q8qp-cvcw-x6jj
transitive, CVSS 7.4, fixed in 1.15.2
https://osv.dev/vulnerability/GHSA-q8qp-cvcw-x6jj - package-lock.jsonaxios 1.15.1 — GHSA-3g43-6gmg-66jw
transitive, CVSS 7.0, fixed in 1.15.2
https://osv.dev/vulnerability/GHSA-3g43-6gmg-66jw - package-lock.jsonaxios 1.15.1 — GHSA-3pq3-5fj3-cg6v
transitive, CVSS 7.0, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-3pq3-5fj3-cg6v - package-lock.jsonaxios 1.15.1 — GHSA-44g4-m2mj-wpvx
transitive, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-44g4-m2mj-wpvx - package-lock.jsonaxios 1.15.1 — GHSA-4hqw-qxg8-jxx2
transitive, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-4hqw-qxg8-jxx2 - package-lock.jsonaxios 1.15.1 — GHSA-9fr6-4gfg-395g
transitive, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-9fr6-4gfg-395g - package-lock.jsonaxios 1.15.1 — GHSA-f4gw-2p7v-4548
transitive, CVSS 6.9, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-f4gw-2p7v-4548 - package-lock.jsonaxios 1.15.1 — GHSA-hcpx-6fm6-wx23
transitive, CVSS 6.9, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-hcpx-6fm6-wx23 - package-lock.jsonaxios 1.15.1 — GHSA-j8rh-479h-cp32
transitive, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-j8rh-479h-cp32 - package-lock.jsonaxios 1.15.1 — GHSA-vh66-26gq-q6x8
transitive, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-vh66-26gq-q6x8 - package-lock.jsonaxios 1.15.1 — GHSA-3w6x-2g7m-8v23
transitive, CVSS 6.5, fixed in 1.15.2
https://osv.dev/vulnerability/GHSA-3w6x-2g7m-8v23 - package-lock.jsonaxios 1.15.1 — GHSA-42h9-826w-cgv3
transitive, CVSS 6.3, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-42h9-826w-cgv3 - package-lock.jsonaxios 1.15.1 — GHSA-7q8q-rj6j-mhjq
transitive, CVSS 6.3, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-7q8q-rj6j-mhjq - package-lock.jsonaxios 1.15.1 — GHSA-jqh4-m9w3-8hp9
transitive, CVSS 6.3, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-jqh4-m9w3-8hp9 - package-lock.jsonaxios 1.15.1 — GHSA-mmx7-hfxf-jppx
transitive, CVSS 6.3, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-mmx7-hfxf-jppx - package-lock.jsonaxios 1.15.1 — GHSA-mwf2-3pr3-8698
transitive, CVSS 6.3, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-mwf2-3pr3-8698 - package-lock.jsonaxios 1.15.1 — GHSA-pmv8-rq9r-6j72
transitive, CVSS 6.3, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-pmv8-rq9r-6j72 - package-lock.jsonqs 6.14.2 — 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.14.2 — GHSA-q8mj-m7cp-5q26
transitive, CVSS 6.3, fixed in 6.15.2
https://osv.dev/vulnerability/GHSA-q8mj-m7cp-5q26 - package-lock.jsonqs 6.14.2 — GHSA-x5fp-wj9c-mxmx
transitive, CVSS 6.3, fixed in 6.16.0
https://osv.dev/vulnerability/GHSA-x5fp-wj9c-mxmx - package-lock.jsonelliptic 6.6.1 — GHSA-848j-6mx2-7j84
transitive, CVSS 5.6
https://osv.dev/vulnerability/GHSA-848j-6mx2-7j84 - package-lock.jsonaxios 1.15.1 — GHSA-898c-q2cr-xwhg
transitive, CVSS 4.8, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-898c-q2cr-xwhg - package-lock.jsonws 8.17.1 — GHSA-58qx-3vcg-4xpx
transitive, CVSS 4.4, fixed in 8.20.1
https://osv.dev/vulnerability/GHSA-58qx-3vcg-4xpx - package-lock.jsonws 8.18.3 — GHSA-58qx-3vcg-4xpx
transitive, CVSS 4.4, fixed in 8.20.1
https://osv.dev/vulnerability/GHSA-58qx-3vcg-4xpx - package-lock.jsonbody-parser 1.20.4 — GHSA-v422-hmwv-36x6
transitive, CVSS 3.7, fixed in 1.20.6
https://osv.dev/vulnerability/GHSA-v422-hmwv-36x6
Maintenance
- recency
last commit 166 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
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
3 authors with >= 5 commits in 12 months
- 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: 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
no CHANGELOG in the fetched source. `03` §7's partial credit for tagged releases carrying release notes is not applied here — that needs the forge API, which this check does not call
- 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.