io.github.rendleyhq/rendley-mcp
version 1.0.1
- scanned 2026-10-16
- source github.com/rendleyhq/rendley-mcp
- commit bc2c0d0bee37
- transport streamable-http
- files read 48
- methodology 0.2.0
- ruleset 0.1.1
No tag matching version 1.0.1 was found in this repository, so the scan read the default branch instead. The findings below describe that code, not necessarily the released version.
87
95
9
70measured on 45% of this axis
29
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/api/client.ts:272mcp-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.
private async request(path: string, init: RequestInit = {}): Promise<Response> { const res = await fetch(this.url(path), { ...init, signal: init.signal ?? AbortSignal.timeout(30_000), - src/api/client.ts:522mcp-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 getEditorSessionToken(projectId: string): Promise<string> { const res = await fetch(this.url("/auth/session-token"), { method: "POST", headers: this.headers, - src/brandkit/upload.ts:56mcp-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 put = await fetch(created.presigned_url, { method: "PUT", headers: { "Content-Type": mimeType }, - src/http/uploads.ts:40mcp-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.
signal: AbortSignal | undefined, ): Promise<{ ok: boolean; status: number; body: string }> { const res = await fetch(presignedUrl, { method: "PUT", body: bytes, - src/utils/url-guard.ts:48mcp-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.
validateExternalUrl(rawUrl); const res = await fetch(rawUrl, { headers: opts.headers, signal: AbortSignal.timeout(opts.timeoutMs),
Auth Posture
- authentication_model
auth enforcement present at a call site in the source (inbound token verification) and documented in the README; "refused without credentials" (`03` §4) established by reading the code rather than by connecting
- transport_security
declared endpoint(s) are HTTPS: https://mcp.rendley.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
credentials are read from the environment (POSTHOG_API_KEY) and documented in the README
- authorization_granularity
18 tool registrations with conditional access logic present in the same source
Dependency Health
Showing the 50 most severe of 55 findings on this axis. The score was computed over all of them — findings beyond the fourth of a severity still deduct at a tenth of their weight — so the remainder is omitted from this page, not from the arithmetic.
- bun.lockproxy-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 - bun.lock@modelcontextprotocol/sdk 1.29.0 — GHSA-6qxp-vccf-f47h
direct, CVSS 7.5, fixed in 1.31.0
https://osv.dev/vulnerability/GHSA-6qxp-vccf-f47h - bun.lockhono 4.12.14 — GHSA-88fw-hqm2-52qc
direct, CVSS 7.1, fixed in 4.12.25
https://osv.dev/vulnerability/GHSA-88fw-hqm2-52qc - bun.lockip-address 10.1.0 — GHSA-mwp4-54f8-5fhr
transitive, CVSS 7.7, fixed in 10.3.1
https://osv.dev/vulnerability/GHSA-mwp4-54f8-5fhr - bun.lockfast-uri 3.1.0 — GHSA-4c8g-83qw-93j6
transitive, CVSS 7.5, fixed in 3.1.3
https://osv.dev/vulnerability/GHSA-4c8g-83qw-93j6 - bun.lockfast-uri 3.1.0 — GHSA-7p8r-x3mc-p8w7
transitive, CVSS 7.5, fixed in 3.1.5
https://osv.dev/vulnerability/GHSA-7p8r-x3mc-p8w7 - bun.lockfast-uri 3.1.0 — GHSA-f65p-4m7j-42xc
transitive, CVSS 7.5, fixed in 3.1.6
https://osv.dev/vulnerability/GHSA-f65p-4m7j-42xc - bun.lockfast-uri 3.1.0 — GHSA-jqff-g426-hqxp
transitive, CVSS 7.5, fixed in 3.1.6
https://osv.dev/vulnerability/GHSA-jqff-g426-hqxp - bun.lockfast-uri 3.1.0 — GHSA-q3j6-qgpj-74h6
transitive, CVSS 7.5, fixed in 3.1.1
https://osv.dev/vulnerability/GHSA-q3j6-qgpj-74h6 - bun.lockfast-uri 3.1.0 — GHSA-qw65-cvwx-89v3
transitive, CVSS 7.5, fixed in 3.1.7
https://osv.dev/vulnerability/GHSA-qw65-cvwx-89v3 - bun.lockfast-uri 3.1.0 — GHSA-v2hh-gcrm-f6hx
transitive, CVSS 7.5, fixed in 3.1.4
https://osv.dev/vulnerability/GHSA-v2hh-gcrm-f6hx - bun.lockfast-uri 3.1.0 — GHSA-v39h-62p7-jpjc
transitive, CVSS 7.5, fixed in 3.1.2
https://osv.dev/vulnerability/GHSA-v39h-62p7-jpjc - bun.lockhono 4.12.14 — GHSA-9vqf-7f2p-gf9v
direct, CVSS 6.5, fixed in 4.12.16
https://osv.dev/vulnerability/GHSA-9vqf-7f2p-gf9v - bun.lockhono 4.12.14 — GHSA-gqvv-2mrq-wpjv
direct, CVSS 6.5, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-gqvv-2mrq-wpjv - bun.lockhono 4.12.30 — GHSA-gqvv-2mrq-wpjv
direct, CVSS 6.5, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-gqvv-2mrq-wpjv - bun.lockhono 4.12.14 — GHSA-hvrm-45r6-mjfj
direct, CVSS 6.5, fixed in 4.12.27
https://osv.dev/vulnerability/GHSA-hvrm-45r6-mjfj - bun.lockhono 4.12.14 — GHSA-rv63-4mwf-qqc2
direct, CVSS 6.5, fixed in 4.12.25
https://osv.dev/vulnerability/GHSA-rv63-4mwf-qqc2 - bun.lockhono 4.12.14 — GHSA-w62v-xxxg-mg59
direct, CVSS 6.1, fixed in 4.12.27
https://osv.dev/vulnerability/GHSA-w62v-xxxg-mg59 - bun.lockhono 4.12.14 — GHSA-crvj-82cr-hjcx
direct, CVSS 5.9, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-crvj-82cr-hjcx - bun.lockhono 4.12.30 — GHSA-crvj-82cr-hjcx
direct, CVSS 5.9, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-crvj-82cr-hjcx - bun.lockhono 4.12.14 — GHSA-wwfh-h76j-fc44
direct, CVSS 5.9, fixed in 4.12.25
https://osv.dev/vulnerability/GHSA-wwfh-h76j-fc44 - bun.lockhono 4.12.14 — GHSA-2gcr-mfcq-wcc3
direct, CVSS 5.3, fixed in 4.12.21
https://osv.dev/vulnerability/GHSA-2gcr-mfcq-wcc3 - bun.lockhono 4.12.14 — GHSA-54fx-42gc-7vw4
direct, CVSS 5.3, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-54fx-42gc-7vw4 - bun.lockhono 4.12.30 — GHSA-54fx-42gc-7vw4
direct, CVSS 5.3, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-54fx-42gc-7vw4 - bun.lockhono 4.12.14 — GHSA-8j4g-w8fx-2239
direct, CVSS 5.3, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-8j4g-w8fx-2239 - bun.lockhono 4.12.30 — GHSA-8j4g-w8fx-2239
direct, CVSS 5.3, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-8j4g-w8fx-2239 - bun.lockhono 4.12.14 — GHSA-g6gw-c38x-mqfc
direct, CVSS 5.3, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-g6gw-c38x-mqfc - bun.lockhono 4.12.30 — GHSA-g6gw-c38x-mqfc
direct, CVSS 5.3, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-g6gw-c38x-mqfc - bun.lockhono 4.12.14 — GHSA-j6c9-x7qj-28xf
direct, CVSS 5.3, fixed in 4.12.25
https://osv.dev/vulnerability/GHSA-j6c9-x7qj-28xf - bun.lockhono 4.12.14 — GHSA-p77w-8qqv-26rm
direct, CVSS 5.3, fixed in 4.12.18
https://osv.dev/vulnerability/GHSA-p77w-8qqv-26rm - bun.lockhono 4.12.14 — GHSA-xrhx-7g5j-rcj5
direct, CVSS 5.3, fixed in 4.12.21
https://osv.dev/vulnerability/GHSA-xrhx-7g5j-rcj5 - bun.lockhono 4.12.14 — GHSA-f23p-vx2j-j53r
direct, CVSS 4.8, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-f23p-vx2j-j53r - bun.lockhono 4.12.30 — GHSA-f23p-vx2j-j53r
direct, CVSS 4.8, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-f23p-vx2j-j53r - bun.lockhono 4.12.14 — GHSA-f577-qrjj-4474
direct, CVSS 4.8, fixed in 4.12.21
https://osv.dev/vulnerability/GHSA-f577-qrjj-4474 - bun.lockhono 4.12.14 — GHSA-wgpf-jwqj-8h8p
direct, CVSS 4.8, fixed in 4.12.25
https://osv.dev/vulnerability/GHSA-wgpf-jwqj-8h8p - bun.lockhono 4.12.14 — GHSA-xgm2-5f3f-mvvc
direct, CVSS 4.8, fixed in 4.12.27
https://osv.dev/vulnerability/GHSA-xgm2-5f3f-mvvc - bun.lockhono 4.12.14 — GHSA-69xw-7hcm-h432
direct, CVSS 4.7, fixed in 4.12.16
https://osv.dev/vulnerability/GHSA-69xw-7hcm-h432 - bun.lockhono 4.12.14 — GHSA-hxh3-vqpv-xpqv
direct, CVSS 4.7, fixed in 4.13.7
https://osv.dev/vulnerability/GHSA-hxh3-vqpv-xpqv - bun.lockhono 4.12.30 — GHSA-hxh3-vqpv-xpqv
direct, CVSS 4.7, fixed in 4.13.7
https://osv.dev/vulnerability/GHSA-hxh3-vqpv-xpqv - bun.lockhono 4.12.14 — GHSA-3hrh-pfw6-9m5x
direct, CVSS 4.3, fixed in 4.12.21
https://osv.dev/vulnerability/GHSA-3hrh-pfw6-9m5x - bun.lockhono 4.12.14 — GHSA-qp7p-654g-cw7p
direct, CVSS 4.3, fixed in 4.12.18
https://osv.dev/vulnerability/GHSA-qp7p-654g-cw7p - bun.lockfast-copy 4.0.3 — GHSA-jggr-w7fw-pc2j
transitive, CVSS 6.3, fixed in 4.1.0
https://osv.dev/vulnerability/GHSA-jggr-w7fw-pc2j - bun.lockip-address 10.1.0 — GHSA-h3mg-xc3c-68pw
transitive, CVSS 6.3, fixed in 10.7.1
https://osv.dev/vulnerability/GHSA-h3mg-xc3c-68pw - bun.lockip-address 10.1.0 — GHSA-j6r3-76f7-8jcv
transitive, CVSS 6.3, fixed in 10.7.1
https://osv.dev/vulnerability/GHSA-j6r3-76f7-8jcv - bun.lockip-address 10.1.0 — GHSA-rpw4-54j3-4h4q
transitive, CVSS 6.3, fixed in 10.5.1
https://osv.dev/vulnerability/GHSA-rpw4-54j3-4h4q - bun.lockqs 6.15.1 — GHSA-4mjr-xmp4-gh2g
transitive, CVSS 6.3, fixed in 6.16.0
https://osv.dev/vulnerability/GHSA-4mjr-xmp4-gh2g - bun.lockqs 6.15.1 — GHSA-q8mj-m7cp-5q26
transitive, CVSS 6.3, fixed in 6.15.2
https://osv.dev/vulnerability/GHSA-q8mj-m7cp-5q26 - bun.lockqs 6.15.1 — GHSA-x5fp-wj9c-mxmx
transitive, CVSS 6.3, fixed in 6.16.0
https://osv.dev/vulnerability/GHSA-x5fp-wj9c-mxmx - bun.lock@hono/node-server 1.19.14 — GHSA-frvp-7c67-39w9
transitive, CVSS 5.9, fixed in 1.19.15
https://osv.dev/vulnerability/GHSA-frvp-7c67-39w9 - bun.lockip-address 10.1.0 — GHSA-v2v4-37r5-5v8g
transitive, CVSS 5.3, fixed in 10.1.1
https://osv.dev/vulnerability/GHSA-v2v4-37r5-5v8g
Maintenance
- recency
last commit 88 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
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
LICENSE present with no SPDX-License-Identifier tag; identified as 'Apache-2.0' from its text
- readme_quality
README.md: 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
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.