io.github.eldesh/random-mcp
version 2.1.0
- scanned 2026-10-16
- source github.com/eldesh/random-mcp
- commit 0177e0288688
- transport streamable-http
- files read 15
- methodology 0.2.0
- ruleset 0.1.1
No tag matching version 2.1.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.
95
80measured on 25% of this axis
36
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/utils.ts:63mcp-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 resp = await fetch(upstream_url, { body: new URLSearchParams({ client_id,
Auth Posture
- authentication_model
no authentication appears in the source we fetched, but this server's network endpoint is a hosted remote, whose authentication can be enforced in front of its code — and no credential header is declared. An undeclared header is not an absent one, so `03` §4's "no authentication" band is not established.
- transport_security
declared endpoint(s) are HTTPS: https://random-mcp.eldesh-tools.workers.dev/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
detect-secrets matched 7 credential-shaped string(s), every one from a keyword or entropy heuristic (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; Hex High Entropy String at worker-configuration.d.ts:11896; Hex High Entropy String at worker-configuration.d.ts:11908; Hex High Entropy String at worker-configuration.d.ts:12044; Hex High Entropy String at worker-configuration.d.ts:12050; Hex High Entropy String at worker-configuration.d.ts:12068; Hex High Entropy String at worker-configuration.d.ts:12074; Hex High Entropy String at wrangler.jsonc:17
- authorization_granularity
6 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.jsonsharp 0.35.2 — 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.35.2 — GHSA-wq5f-xc86-pv6w
transitive, CVSS 8.9, fixed in 0.35.5
https://osv.dev/vulnerability/GHSA-wq5f-xc86-pv6w - package-lock.json@modelcontextprotocol/client 2.0.0 — GHSA-6qxp-vccf-f47h
transitive, CVSS 7.5, fixed in 2.2.0
https://osv.dev/vulnerability/GHSA-6qxp-vccf-f47h - package-lock.json@modelcontextprotocol/sdk 1.30.0 — GHSA-6qxp-vccf-f47h
transitive, CVSS 7.5, fixed in 1.31.0
https://osv.dev/vulnerability/GHSA-6qxp-vccf-f47h - package-lock.jsonfast-uri 3.1.5 — GHSA-5jgf-p345-68v8
transitive, CVSS 7.5, fixed in 3.1.6
https://osv.dev/vulnerability/GHSA-5jgf-p345-68v8 - package-lock.jsonfast-uri 3.1.5 — GHSA-f65p-4m7j-42xc
transitive, CVSS 7.5, fixed in 3.1.6
https://osv.dev/vulnerability/GHSA-f65p-4m7j-42xc - package-lock.jsonfast-uri 3.1.5 — GHSA-fph4-wmhf-6fwf
transitive, CVSS 7.5, fixed in 3.1.6
https://osv.dev/vulnerability/GHSA-fph4-wmhf-6fwf - package-lock.jsonfast-uri 3.1.5 — GHSA-jqff-g426-hqxp
transitive, CVSS 7.5, fixed in 3.1.6
https://osv.dev/vulnerability/GHSA-jqff-g426-hqxp - package-lock.jsonfast-uri 3.1.5 — GHSA-qw65-cvwx-89v3
transitive, CVSS 7.5, fixed in 3.1.7
https://osv.dev/vulnerability/GHSA-qw65-cvwx-89v3 - package-lock.jsonundici 7.29.0 — GHSA-rfgv-xxqx-mfg5
transitive, CVSS 7.5, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-rfgv-xxqx-mfg5 - package-lock.jsonundici 7.29.0 — GHSA-w293-vg96-wgc3
transitive, CVSS 7.4, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-w293-vg96-wgc3 - package-lock.jsonhono 4.12.27 — GHSA-gqvv-2mrq-wpjv
direct, CVSS 6.5, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-gqvv-2mrq-wpjv - package-lock.jsonhono 4.12.27 — GHSA-crvj-82cr-hjcx
direct, CVSS 5.9, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-crvj-82cr-hjcx - package-lock.jsonhono 4.12.27 — GHSA-54fx-42gc-7vw4
direct, CVSS 5.3, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-54fx-42gc-7vw4 - package-lock.jsonhono 4.12.27 — GHSA-8j4g-w8fx-2239
direct, CVSS 5.3, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-8j4g-w8fx-2239 - package-lock.jsonhono 4.12.27 — GHSA-g6gw-c38x-mqfc
direct, CVSS 5.3, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-g6gw-c38x-mqfc - package-lock.jsonhono 4.12.27 — GHSA-f23p-vx2j-j53r
direct, CVSS 4.8, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-f23p-vx2j-j53r - package-lock.jsonhono 4.12.27 — GHSA-hxh3-vqpv-xpqv
direct, CVSS 4.7, fixed in 4.13.7
https://osv.dev/vulnerability/GHSA-hxh3-vqpv-xpqv - 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.jsonundici 7.29.0 — GHSA-2jfj-6hjv-fm6j
transitive, CVSS 6.5, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-2jfj-6hjv-fm6j - 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.jsonundici 7.29.0 — GHSA-3wwx-pv8p-q78v
transitive, CVSS 5.9, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-3wwx-pv8p-q78v - package-lock.jsonundici 7.29.0 — GHSA-3xpg-4rpp-hhhm
transitive, CVSS 5.9, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-3xpg-4rpp-hhhm - package-lock.jsonundici 7.29.0 — GHSA-pmjh-fq2x-6v4x
transitive, CVSS 5.9, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-pmjh-fq2x-6v4x - package-lock.jsonundici 7.29.0 — GHSA-rx4f-c7p8-82vq
transitive, CVSS 5.9, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-rx4f-c7p8-82vq - package-lock.jsonfast-uri 3.1.5 — 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.12.27 — GHSA-79qm-7rj5-m7r9
direct, CVSS 3.7, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-79qm-7rj5-m7r9 - package-lock.jsonundici 7.29.0 — GHSA-2gqq-gqf2-x968
transitive, CVSS 3.7, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-2gqq-gqf2-x968 - package-lock.jsonundici 7.29.0 — GHSA-8436-99hf-9mmv
transitive, CVSS 3.7, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-8436-99hf-9mmv - package-lock.jsonundici 7.29.0 — GHSA-r53p-7pc4-xj5r
transitive, CVSS 3.7, fixed in 7.29.1
https://osv.dev/vulnerability/GHSA-r53p-7pc4-xj5r
Maintenance
- recency
last commit 48 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 'MIT' 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.