ai.smithery/BigVik193-reddit-ads-mcp-api
version 1.0.0
- scanned 2026-10-16
- source github.com/BigVik193/reddit-ads-mcp-api
- commit dbcf47d5a043
- transport streamable-http
- files read 1
- 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.
100
80measured on 65% of this axis
0
10measured on 45% of this axis
8
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.
Auth Posture
- authentication_model
credential enforcement present in source but not documented in the README
- transport_security
declared endpoint(s) are HTTPS: https://server.smithery.ai/@BigVik193/reddit-ads-mcp-api/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 1 credential-shaped string(s), every one from a keyword or entropy heuristic (Base64 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 .smithery/index.cjs:12701
- authorization_granularity
11 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
Showing the 50 most severe of 65 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.
- 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.18.0 — GHSA-8r9q-7v3j-jr4g
direct, CVSS 8.7, fixed in 1.25.2
https://osv.dev/vulnerability/GHSA-8r9q-7v3j-jr4g - package-lock.jsonaxios 1.12.1 — GHSA-35jp-ww65-95wh
direct, CVSS 8.7, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-35jp-ww65-95wh - package-lock.jsonform-data 4.0.4 — GHSA-hmw2-7cc7-3qxx
direct, CVSS 8.7, fixed in 4.0.6
https://osv.dev/vulnerability/GHSA-hmw2-7cc7-3qxx - package-lock.jsonaxios 1.12.1 — GHSA-p92q-9vqr-4j8v
direct, CVSS 8.2, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-p92q-9vqr-4j8v - package-lock.json@modelcontextprotocol/sdk 1.18.0 — GHSA-w48q-cv73-mx4w
direct, CVSS 7.6, fixed in 1.24.0
https://osv.dev/vulnerability/GHSA-w48q-cv73-mx4w - package-lock.json@modelcontextprotocol/sdk 1.18.0 — GHSA-6qxp-vccf-f47h
direct, CVSS 7.5, fixed in 1.31.0
https://osv.dev/vulnerability/GHSA-6qxp-vccf-f47h - package-lock.jsonaxios 1.12.1 — GHSA-43fc-jf86-j433
direct, CVSS 7.5, fixed in 1.13.5
https://osv.dev/vulnerability/GHSA-43fc-jf86-j433 - package-lock.jsonaxios 1.12.1 — GHSA-62hf-57xw-28j9
direct, CVSS 7.5, fixed in 1.15.1
https://osv.dev/vulnerability/GHSA-62hf-57xw-28j9 - package-lock.jsonaxios 1.12.1 — GHSA-777c-7fjr-54vf
direct, CVSS 7.5, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-777c-7fjr-54vf - package-lock.jsonaxios 1.12.1 — GHSA-hfxv-24rg-xrqf
direct, CVSS 7.5, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-hfxv-24rg-xrqf - package-lock.jsonaxios 1.12.1 — GHSA-j5f8-grm9-p9fc
direct, CVSS 7.5, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-j5f8-grm9-p9fc - package-lock.jsonaxios 1.12.1 — GHSA-6chq-wfr3-2hj9
direct, CVSS 7.4, fixed in 1.15.1
https://osv.dev/vulnerability/GHSA-6chq-wfr3-2hj9 - package-lock.jsonaxios 1.12.1 — GHSA-pf86-5x62-jrwf
direct, CVSS 7.4, fixed in 1.15.1
https://osv.dev/vulnerability/GHSA-pf86-5x62-jrwf - package-lock.jsonaxios 1.12.1 — GHSA-q8qp-cvcw-x6jj
direct, CVSS 7.4, fixed in 1.15.2
https://osv.dev/vulnerability/GHSA-q8qp-cvcw-x6jj - package-lock.jsonaxios 1.12.1 — GHSA-pmwg-cvhr-8vh7
direct, CVSS 7.2, fixed in 1.15.1
https://osv.dev/vulnerability/GHSA-pmwg-cvhr-8vh7 - package-lock.json@modelcontextprotocol/sdk 1.18.0 — GHSA-345p-7cg4-v4c7
direct, CVSS 7.1, fixed in 1.26.0
https://osv.dev/vulnerability/GHSA-345p-7cg4-v4c7 - package-lock.jsonaxios 1.12.1 — GHSA-3g43-6gmg-66jw
direct, CVSS 7.0, fixed in 1.15.2
https://osv.dev/vulnerability/GHSA-3g43-6gmg-66jw - package-lock.jsonbraces 3.0.3 — GHSA-vfj7-8cjw-p6xm
transitive, CVSS 8.7
https://osv.dev/vulnerability/GHSA-vfj7-8cjw-p6xm - package-lock.jsonjsondiffpatch 0.6.0 — GHSA-j4fx-xxwh-2485
transitive, CVSS 8.2, fixed in 0.7.6
https://osv.dev/vulnerability/GHSA-j4fx-xxwh-2485 - package-lock.jsonnanoid 3.3.11 — GHSA-28wg-ghj8-5hjv
transitive, CVSS 8.2, fixed in 3.3.16
https://osv.dev/vulnerability/GHSA-28wg-ghj8-5hjv - package-lock.jsonnanoid 3.3.11 — 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.4.2 — GHSA-7w5x-hrqm-74c2
transitive, CVSS 8.2, fixed in 1.7.1
https://osv.dev/vulnerability/GHSA-7w5x-hrqm-74c2 - package-lock.jsonlodash 4.17.21 — GHSA-r5fr-rjxr-66jc
transitive, CVSS 8.1, fixed in 4.18.0
https://osv.dev/vulnerability/GHSA-r5fr-rjxr-66jc - package-lock.jsonpath-to-regexp 8.3.0 — GHSA-j3q9-mxjg-w52f
transitive, CVSS 7.5, fixed in 8.4.0
https://osv.dev/vulnerability/GHSA-j3q9-mxjg-w52f - package-lock.jsonpicomatch 2.3.1 — GHSA-c2c7-rcm5-vvqj
transitive, CVSS 7.5, fixed in 2.3.2
https://osv.dev/vulnerability/GHSA-c2c7-rcm5-vvqj - package-lock.jsonuuid 11.1.0 — GHSA-w5hq-g745-h8pq
transitive, CVSS 7.5, fixed in 11.1.1
https://osv.dev/vulnerability/GHSA-w5hq-g745-h8pq - package-lock.jsonnanoid 3.3.11 — GHSA-xwg4-73v4-xw9w
transitive, CVSS 7.4, fixed in 3.3.12
https://osv.dev/vulnerability/GHSA-xwg4-73v4-xw9w - package-lock.jsonaxios 1.12.1 — GHSA-4hqw-qxg8-jxx2
direct, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-4hqw-qxg8-jxx2 - package-lock.jsonaxios 1.12.1 — GHSA-9fr6-4gfg-395g
direct, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-9fr6-4gfg-395g - package-lock.jsonaxios 1.12.1 — GHSA-j8rh-479h-cp32
direct, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-j8rh-479h-cp32 - package-lock.jsonaxios 1.12.1 — GHSA-vh66-26gq-q6x8
direct, CVSS 6.9, fixed in 1.20.0
https://osv.dev/vulnerability/GHSA-vh66-26gq-q6x8 - package-lock.jsonaxios 1.12.1 — GHSA-m7pr-hjqh-92cm
direct, CVSS 6.8, fixed in 1.15.1
https://osv.dev/vulnerability/GHSA-m7pr-hjqh-92cm - package-lock.jsonaxios 1.12.1 — GHSA-3w6x-2g7m-8v23
direct, CVSS 6.5, fixed in 1.15.2
https://osv.dev/vulnerability/GHSA-3w6x-2g7m-8v23 - package-lock.jsonaxios 1.12.1 — GHSA-3p68-rc4w-qgx5
direct, CVSS 6.3, fixed in 1.15.0
https://osv.dev/vulnerability/GHSA-3p68-rc4w-qgx5 - package-lock.jsonaxios 1.12.1 — GHSA-42h9-826w-cgv3
direct, CVSS 6.3, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-42h9-826w-cgv3 - package-lock.jsonaxios 1.12.1 — GHSA-7q8q-rj6j-mhjq
direct, CVSS 6.3, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-7q8q-rj6j-mhjq - package-lock.jsonaxios 1.12.1 — GHSA-jqh4-m9w3-8hp9
direct, CVSS 6.3, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-jqh4-m9w3-8hp9 - package-lock.jsonaxios 1.12.1 — GHSA-mmx7-hfxf-jppx
direct, CVSS 6.3, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-mmx7-hfxf-jppx - package-lock.jsonaxios 1.12.1 — GHSA-pmv8-rq9r-6j72
direct, CVSS 6.3, fixed in 1.18.0
https://osv.dev/vulnerability/GHSA-pmv8-rq9r-6j72 - package-lock.jsonaxios 1.12.1 — GHSA-xx6v-rp6x-q39c
direct, CVSS 5.4, fixed in 1.15.1
https://osv.dev/vulnerability/GHSA-xx6v-rp6x-q39c - package-lock.jsonaxios 1.12.1 — GHSA-445q-vr5w-6q77
direct, CVSS 5.3, fixed in 1.15.1
https://osv.dev/vulnerability/GHSA-445q-vr5w-6q77 - package-lock.jsonaxios 1.12.1 — GHSA-5c9x-8gcm-mpgx
direct, CVSS 5.3, fixed in 1.15.1
https://osv.dev/vulnerability/GHSA-5c9x-8gcm-mpgx - package-lock.jsonaxios 1.12.1 — GHSA-vf2m-468p-8v99
direct, CVSS 5.3, fixed in 1.15.1
https://osv.dev/vulnerability/GHSA-vf2m-468p-8v99 - package-lock.jsonaxios 1.12.1 — GHSA-898c-q2cr-xwhg
direct, CVSS 4.8, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-898c-q2cr-xwhg - package-lock.jsonaxios 1.12.1 — GHSA-fvcv-3m26-pcqx
direct, CVSS 4.8, fixed in 1.15.0
https://osv.dev/vulnerability/GHSA-fvcv-3m26-pcqx - package-lock.jsonaxios 1.12.1 — GHSA-w9j2-pvgh-6h63
direct, CVSS 4.8, fixed in 1.15.1
https://osv.dev/vulnerability/GHSA-w9j2-pvgh-6h63 - package-lock.jsonfollow-redirects 1.15.11 — GHSA-r4q5-vmmm-2653
transitive, CVSS 6.9, fixed in 1.16.0
https://osv.dev/vulnerability/GHSA-r4q5-vmmm-2653 - package-lock.jsonlodash 4.17.21 — GHSA-f23m-r3pf-42rh
transitive, CVSS 6.9, fixed in 4.18.0
https://osv.dev/vulnerability/GHSA-f23m-r3pf-42rh - package-lock.jsonqs 6.14.0 — GHSA-4mjr-xmp4-gh2g
transitive, CVSS 6.3, fixed in 6.16.0
https://osv.dev/vulnerability/GHSA-4mjr-xmp4-gh2g
Maintenance
- recency
last commit 396 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
no author reached `03` §5's 5-commit bar in the last 12 months (0 contributor(s) with fewer) — scored at §5's weakest described band, which the section defines for a quiet 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
package.json declares 'ISC' but no LICENSE file ships with the source
- readme_quality
no README in the fetched source
- 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.