ai.gregbenza/openhouse
version 1.0.0
- scanned 2026-10-16
- source github.com/TheNonduality/gregbenza-ai
- commit 945593a9e151
- transport streamable-http
- files read 51
- methodology 0.2.0
- ruleset 0.1.1
No tag matching version 1.0.0 was found in this repository, so the scan read the default branch instead. The findings below describe that code, not necessarily the released version.
91measured on 98% of this axis
1 file could not be parsed and was not scanned
52measured on 85% of this axis
8
74measured on 70% of this axis
0
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
- netlify/_parked/waystation-mcp.mjs:64mcp-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.
async function fetchText(p) { const r = await fetch(SITE + p); if (!r.ok) throw new Error(`${p}: ${r.status}`); return r.text(); - public/live.js:208mcp-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.
if (document.hidden) return wait(); try { const res = await fetch(location.href, { cache: 'no-store', credentials: 'same-origin' }); if (!res.ok) throw new Error(String(res.status)); const doc = new DOMParser().parseFromString(await res.text(), 'text/html');
Auth Posture
- authentication_model
source reads a credential header but no enforcing middleware or rejection path was found — `03` §4's "present but optional or trivially bypassable" band
- transport_security
declared endpoint(s) are HTTPS: https://gregbenza.ai/mcp/openhouse; 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
AWS Access Key at parked/public-projects/pico-repair/rebuild_moov.py:32; …and 4 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. A tool-list handler IS present, so the tools are built in a shape this counter could not enumerate.
Dependency Health
- package-lock.jsonastro 5.18.2 — GHSA-26w7-cxv4-gfx2
direct, CVSS 9.8, fixed in 7.2.8
https://osv.dev/vulnerability/GHSA-26w7-cxv4-gfx2 - package-lock.jsonastro 5.18.2 — GHSA-2pvr-wf23-7pc7
direct, CVSS 7.5, fixed in 6.4.6
https://osv.dev/vulnerability/GHSA-2pvr-wf23-7pc7 - package-lock.jsonastro 5.18.2 — GHSA-8hv8-536x-4wqp
direct, CVSS 7.1, fixed in 6.3.3
https://osv.dev/vulnerability/GHSA-8hv8-536x-4wqp - package-lock.jsonsharp 0.34.5 — GHSA-rgj7-g3m4-5g8c
transitive, CVSS 8.9, fixed in 0.35.4
https://osv.dev/vulnerability/GHSA-rgj7-g3m4-5g8c - package-lock.jsonsharp 0.34.5 — GHSA-wq5f-xc86-pv6w
transitive, CVSS 8.9, fixed in 0.35.5
https://osv.dev/vulnerability/GHSA-wq5f-xc86-pv6w - package-lock.jsonhttp-cache-semantics 4.2.0 — GHSA-ch52-4w7c-c8xp
transitive, CVSS 8.7
https://osv.dev/vulnerability/GHSA-ch52-4w7c-c8xp - package-lock.jsonimage-size 2.0.2 — GHSA-5p2g-fcmc-qvqq
transitive, CVSS 8.7, fixed in 2.0.3
https://osv.dev/vulnerability/GHSA-5p2g-fcmc-qvqq - package-lock.jsonimage-size 2.0.2 — GHSA-w3rx-r6r6-pgpr
transitive, CVSS 8.7, fixed in 2.0.3
https://osv.dev/vulnerability/GHSA-w3rx-r6r6-pgpr - package-lock.jsonsource-map-js 1.2.1 — GHSA-68fv-2mgg-jv7q
transitive, CVSS 8.7, fixed in 1.2.2
https://osv.dev/vulnerability/GHSA-68fv-2mgg-jv7q - package-lock.jsondevalue 5.8.2 — GHSA-mcm9-63f2-9j32
transitive, CVSS 8.2, fixed in 5.9.3
https://osv.dev/vulnerability/GHSA-mcm9-63f2-9j32 - package-lock.jsondevalue 5.8.2 — GHSA-r9w8-h9r3-54w4
transitive, CVSS 8.2, fixed in 5.9.3
https://osv.dev/vulnerability/GHSA-r9w8-h9r3-54w4 - package-lock.jsondevalue 5.8.2 — GHSA-x5rw-q4pp-hg5g
transitive, CVSS 8.2, fixed in 5.9.3
https://osv.dev/vulnerability/GHSA-x5rw-q4pp-hg5g - package-lock.jsonnanoid 3.3.16 — GHSA-2v37-7h3g-55p8
transitive, CVSS 8.2, fixed in 3.3.18
https://osv.dev/vulnerability/GHSA-2v37-7h3g-55p8 - package-lock.jsonsmol-toml 1.7.0 — GHSA-7w5x-hrqm-74c2
transitive, CVSS 8.2, fixed in 1.7.1
https://osv.dev/vulnerability/GHSA-7w5x-hrqm-74c2 - package-lock.jsonsvgo 4.0.2 — GHSA-w27v-7q3p-w38r
transitive, CVSS 8.2, fixed in 4.1.0
https://osv.dev/vulnerability/GHSA-w27v-7q3p-w38r - package-lock.json@fastify/busboy 3.2.0 — GHSA-x8mw-p69m-v3mx
transitive, CVSS 7.5, fixed in 3.2.1
https://osv.dev/vulnerability/GHSA-x8mw-p69m-v3mx - package-lock.json@fastify/busboy 3.2.0 — GHSA-xjh9-v7x6-24jw
transitive, CVSS 7.5, fixed in 3.2.1
https://osv.dev/vulnerability/GHSA-xjh9-v7x6-24jw - package-lock.jsondevalue 5.8.2 — GHSA-j22f-vq7h-c4qm
transitive, CVSS 7.5, fixed in 5.9.3
https://osv.dev/vulnerability/GHSA-j22f-vq7h-c4qm - package-lock.jsonjs-yaml 4.3.0 — GHSA-2883-xcg3-v3hh
transitive, CVSS 7.5, fixed in 4.3.2
https://osv.dev/vulnerability/GHSA-2883-xcg3-v3hh - package-lock.jsonjs-yaml 4.3.0 — GHSA-5p4m-2wfm-xmqj
transitive, CVSS 7.5, fixed in 4.3.1
https://osv.dev/vulnerability/GHSA-5p4m-2wfm-xmqj - package-lock.jsonsharp 0.34.5 — GHSA-f88m-g3jw-g9cj
transitive, CVSS 7.0, fixed in 0.35.0
https://osv.dev/vulnerability/GHSA-f88m-g3jw-g9cj - package-lock.jsonastro 5.18.2 — GHSA-376h-93r7-7g6f
direct, CVSS 6.3, fixed in 7.2.4
https://osv.dev/vulnerability/GHSA-376h-93r7-7g6f - package-lock.jsonastro 5.18.2 — GHSA-j687-52p2-xcff
direct, CVSS 6.1, fixed in 6.1.6
https://osv.dev/vulnerability/GHSA-j687-52p2-xcff - package-lock.jsonastro 5.18.2 — GHSA-xr5h-phrj-8vxv
direct, CVSS 6.1, fixed in 6.1.10
https://osv.dev/vulnerability/GHSA-xr5h-phrj-8vxv - package-lock.jsonastro 5.18.2 — GHSA-4g3v-8h47-v7g6
direct, CVSS 5.3, fixed in 7.1.0
https://osv.dev/vulnerability/GHSA-4g3v-8h47-v7g6 - package-lock.jsonastro 5.18.2 — GHSA-f48w-9m4c-m7f5
direct, CVSS 5.1, fixed in 7.0.6
https://osv.dev/vulnerability/GHSA-f48w-9m4c-m7f5 - package-lock.jsonastro 5.18.2 — GHSA-jrpj-wcv7-9fh9
direct, CVSS 4.2, fixed in 6.4.6
https://osv.dev/vulnerability/GHSA-jrpj-wcv7-9fh9 - package-lock.jsondevalue 5.8.2 — GHSA-4q55-j62x-fr9h
transitive, CVSS 6.3, fixed in 5.9.3
https://osv.dev/vulnerability/GHSA-4q55-j62x-fr9h - package-lock.jsondevalue 5.8.2 — GHSA-hx4r-w6wj-j8fg
transitive, CVSS 6.3, fixed in 5.9.3
https://osv.dev/vulnerability/GHSA-hx4r-w6wj-j8fg - package-lock.jsonpostcss 8.5.22 — GHSA-fxqj-rqcc-2cmp
transitive, CVSS 6.3, fixed in 8.5.23
https://osv.dev/vulnerability/GHSA-fxqj-rqcc-2cmp - package-lock.jsonsvgo 4.0.2 — GHSA-4vpr-x523-8j87
transitive, CVSS 6.1, fixed in 4.1.0
https://osv.dev/vulnerability/GHSA-4vpr-x523-8j87 - package-lock.json@fastify/busboy 3.2.0 — GHSA-gxm5-99cw-xjw9
transitive, CVSS 5.8, fixed in 3.2.2
https://osv.dev/vulnerability/GHSA-gxm5-99cw-xjw9 - package-lock.json@opentelemetry/core 2.7.1 — GHSA-8988-4f7v-96qf
transitive, CVSS 5.3, fixed in 2.8.0
https://osv.dev/vulnerability/GHSA-8988-4f7v-96qf - package-lock.jsondevalue 5.8.2 — GHSA-9rgm-9g3h-6x36
transitive, CVSS 5.3, fixed in 5.9.2
https://osv.dev/vulnerability/GHSA-9rgm-9g3h-6x36 - package-lock.jsonsmol-toml 1.7.0 — GHSA-r4xh-jqrq-34v2
transitive, CVSS 5.3, fixed in 1.9.0
https://osv.dev/vulnerability/GHSA-r4xh-jqrq-34v2 - package-lock.jsonastro 5.18.2 — GHSA-7pw4-f3q4-r2p2
direct, CVSS 2.1, fixed in 7.0.4
https://osv.dev/vulnerability/GHSA-7pw4-f3q4-r2p2 - package-lock.jsonesbuild 0.27.7 — GHSA-g7r4-m6w7-qqqr
transitive, CVSS 2.5, fixed in 0.28.1
https://osv.dev/vulnerability/GHSA-g7r4-m6w7-qqqr - package-lock.jsondevalue 5.8.2 — GHSA-wf3x-273g-mvxv
transitive, CVSS 2.3, fixed in 5.9.3
https://osv.dev/vulnerability/GHSA-wf3x-273g-mvxv
Maintenance
- recency
last commit 31 day(s) before 2026-10-16
- issue_responsiveness
median over 4 issue(s) in the last 6 months: 6.6 day(s) to first maintainer comment
- release_cadence
this repository publishes neither releases nor version tags
- 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
no LICENSE file and no license field in any package manifest — `03` §7: without a license, a consumer has no grant to use the server at all
- readme_quality
README.md: over the size floor but none of `03` §7's content heuristics matched
- 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.