ai.smithery/sebastianall1977-gmail-mcp
version 1.7.4
- scanned 2026-10-16
- source github.com/sebastianall1977/gmail-mcp
- commit 66b06b969b1e
- transport streamable-http
- files read 5
- methodology 0.2.0
- ruleset 0.1.1
No tag matching version 1.7.4 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
88measured on 40% of this axis
0
10measured on 45% of this axis
50
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
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://server.smithery.ai/@sebastianall1977/gmail-mcp/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 737 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 pnpm-lock.yaml:67; Base64 High Entropy String at pnpm-lock.yaml:73; Base64 High Entropy String at pnpm-lock.yaml:77; Base64 High Entropy String at pnpm-lock.yaml:87; Base64 High Entropy String at pnpm-lock.yaml:93; Base64 High Entropy String at pnpm-lock.yaml:97; Base64 High Entropy String at pnpm-lock.yaml:100; Base64 High Entropy String at pnpm-lock.yaml:104; Base64 High Entropy String at pnpm-lock.yaml:108; Base64 High Entropy String at pnpm-lock.yaml:112; …and 727 more matches
- authorization_granularity
1 tool registration(s) detected — at or below `03` §4's threshold of 3, so there is no multi-tool surface to segregate
Dependency Health
Showing the 50 most severe of 82 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.
- pnpm-lock.yamlprotobufjs 7.5.3 — GHSA-xq3m-2v4x-88gg
transitive, CVSS 9.8, fixed in 7.5.5
https://osv.dev/vulnerability/GHSA-xq3m-2v4x-88gg - pnpm-lock.yamlproxy-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 - pnpm-lock.yaml@modelcontextprotocol/sdk 1.16.0 — GHSA-8r9q-7v3j-jr4g
direct, CVSS 8.7, fixed in 1.25.2
https://osv.dev/vulnerability/GHSA-8r9q-7v3j-jr4g - pnpm-lock.yaml@modelcontextprotocol/sdk 1.16.0 — GHSA-w48q-cv73-mx4w
direct, CVSS 7.6, fixed in 1.24.0
https://osv.dev/vulnerability/GHSA-w48q-cv73-mx4w - pnpm-lock.yaml@modelcontextprotocol/sdk 1.16.0 — GHSA-6qxp-vccf-f47h
direct, CVSS 7.5, fixed in 1.31.0
https://osv.dev/vulnerability/GHSA-6qxp-vccf-f47h - pnpm-lock.yaml@modelcontextprotocol/sdk 1.16.0 — GHSA-345p-7cg4-v4c7
direct, CVSS 7.1, fixed in 1.26.0
https://osv.dev/vulnerability/GHSA-345p-7cg4-v4c7 - pnpm-lock.yamlbraces 3.0.3 — GHSA-vfj7-8cjw-p6xm
transitive, CVSS 8.7
https://osv.dev/vulnerability/GHSA-vfj7-8cjw-p6xm - pnpm-lock.yamlform-data 4.0.4 — GHSA-hmw2-7cc7-3qxx
transitive, CVSS 8.7, fixed in 4.0.6
https://osv.dev/vulnerability/GHSA-hmw2-7cc7-3qxx - pnpm-lock.yamlminimatch 3.1.2 — GHSA-3ppc-4f35-3m26
transitive, CVSS 8.7, fixed in 3.1.3
https://osv.dev/vulnerability/GHSA-3ppc-4f35-3m26 - pnpm-lock.yaml@babel/plugin-transform-modules-systemjs 7.27.1 — GHSA-fv7c-fp4j-7gwp
transitive, CVSS 8.2, fixed in 7.29.4
https://osv.dev/vulnerability/GHSA-fv7c-fp4j-7gwp - pnpm-lock.yamljsondiffpatch 0.6.0 — GHSA-j4fx-xxwh-2485
transitive, CVSS 8.2, fixed in 0.7.6
https://osv.dev/vulnerability/GHSA-j4fx-xxwh-2485 - pnpm-lock.yamlnanoid 3.3.11 — GHSA-28wg-ghj8-5hjv
transitive, CVSS 8.2, fixed in 3.3.16
https://osv.dev/vulnerability/GHSA-28wg-ghj8-5hjv - pnpm-lock.yamlnanoid 3.3.11 — GHSA-2v37-7h3g-55p8
transitive, CVSS 8.2, fixed in 3.3.18
https://osv.dev/vulnerability/GHSA-2v37-7h3g-55p8 - pnpm-lock.yamllodash 4.17.21 — GHSA-r5fr-rjxr-66jc
transitive, CVSS 8.1, fixed in 4.18.0
https://osv.dev/vulnerability/GHSA-r5fr-rjxr-66jc - pnpm-lock.yamlprotobufjs 7.5.3 — GHSA-75px-5xx7-5xc7
transitive, CVSS 8.1, fixed in 7.5.6
https://osv.dev/vulnerability/GHSA-75px-5xx7-5xc7 - pnpm-lock.yamlbrace-expansion 1.1.12 — GHSA-3jxr-9vmj-r5cp
transitive, CVSS 7.7, fixed in 1.1.16
https://osv.dev/vulnerability/GHSA-3jxr-9vmj-r5cp - pnpm-lock.yamlprotobufjs 7.5.3 — GHSA-66ff-xgx4-vchm
transitive, CVSS 7.7, fixed in 7.5.6
https://osv.dev/vulnerability/GHSA-66ff-xgx4-vchm - pnpm-lock.yamltmp 0.0.33 — GHSA-ph9p-34f9-6g65
transitive, CVSS 7.7, fixed in 0.2.6
https://osv.dev/vulnerability/GHSA-ph9p-34f9-6g65 - pnpm-lock.yaml@grpc/grpc-js 1.13.4 — GHSA-5375-pq7m-f5r2
transitive, CVSS 7.5, fixed in 1.13.5
https://osv.dev/vulnerability/GHSA-5375-pq7m-f5r2 - pnpm-lock.yaml@grpc/grpc-js 1.13.4 — GHSA-99f4-grh7-6pcq
transitive, CVSS 7.5, fixed in 1.13.5
https://osv.dev/vulnerability/GHSA-99f4-grh7-6pcq - pnpm-lock.yaml@opentelemetry/auto-instrumentations-node 0.46.1 — GHSA-q7rr-3cgh-j5r3
transitive, CVSS 7.5, fixed in 0.75.0
https://osv.dev/vulnerability/GHSA-q7rr-3cgh-j5r3 - pnpm-lock.yaml@opentelemetry/propagator-jaeger 1.24.1 — GHSA-45rx-2jwx-cxfr
transitive, CVSS 7.5, fixed in 2.9.0
https://osv.dev/vulnerability/GHSA-45rx-2jwx-cxfr - pnpm-lock.yaml@opentelemetry/sdk-node 0.51.1 — GHSA-q7rr-3cgh-j5r3
transitive, CVSS 7.5, fixed in 0.217.0
https://osv.dev/vulnerability/GHSA-q7rr-3cgh-j5r3 - pnpm-lock.yamlbrace-expansion 1.1.12 — GHSA-6j4f-fj2g-mc7p
transitive, CVSS 7.5, fixed in 1.1.19
https://osv.dev/vulnerability/GHSA-6j4f-fj2g-mc7p - pnpm-lock.yamlbrace-expansion 1.1.12 — GHSA-mh99-v99m-4gvg
transitive, CVSS 7.5, fixed in 1.1.17
https://osv.dev/vulnerability/GHSA-mh99-v99m-4gvg - pnpm-lock.yamlbrace-expansion 1.1.12 — GHSA-qhr7-859c-m2p7
transitive, CVSS 7.5, fixed in 1.1.20
https://osv.dev/vulnerability/GHSA-qhr7-859c-m2p7 - pnpm-lock.yamlbrace-expansion 1.1.12 — GHSA-rgw5-rvv9-x895
transitive, CVSS 7.5, fixed in 1.1.18
https://osv.dev/vulnerability/GHSA-rgw5-rvv9-x895 - pnpm-lock.yamlbrowserslist 4.25.1 — GHSA-73wf-gq98-2v4g
transitive, CVSS 7.5, fixed in 4.28.7
https://osv.dev/vulnerability/GHSA-73wf-gq98-2v4g - pnpm-lock.yamlbrowserslist 4.25.1 — GHSA-c83g-rgw3-j3cx
transitive, CVSS 7.5, fixed in 4.28.7
https://osv.dev/vulnerability/GHSA-c83g-rgw3-j3cx - pnpm-lock.yamljs-yaml 3.14.1 — GHSA-2883-xcg3-v3hh
transitive, CVSS 7.5, fixed in 3.15.2
https://osv.dev/vulnerability/GHSA-2883-xcg3-v3hh - pnpm-lock.yamljs-yaml 3.14.1 — GHSA-52cp-r559-cp3m
transitive, CVSS 7.5, fixed in 3.15.0
https://osv.dev/vulnerability/GHSA-52cp-r559-cp3m - pnpm-lock.yamljs-yaml 3.14.1 — GHSA-5p4m-2wfm-xmqj
transitive, CVSS 7.5, fixed in 3.15.1
https://osv.dev/vulnerability/GHSA-5p4m-2wfm-xmqj - pnpm-lock.yamljws 4.0.0 — GHSA-869p-cjfg-cm3x
transitive, CVSS 7.5, fixed in 4.0.1
https://osv.dev/vulnerability/GHSA-869p-cjfg-cm3x - pnpm-lock.yamlminimatch 3.1.2 — GHSA-23c5-xmqv-rm74
transitive, CVSS 7.5, fixed in 3.1.4
https://osv.dev/vulnerability/GHSA-23c5-xmqv-rm74 - pnpm-lock.yamlminimatch 3.1.2 — GHSA-7r86-cg39-jmmj
transitive, CVSS 7.5, fixed in 3.1.3
https://osv.dev/vulnerability/GHSA-7r86-cg39-jmmj - pnpm-lock.yamlpath-to-regexp 8.2.0 — GHSA-j3q9-mxjg-w52f
transitive, CVSS 7.5, fixed in 8.4.0
https://osv.dev/vulnerability/GHSA-j3q9-mxjg-w52f - pnpm-lock.yamlpicomatch 2.3.1 — GHSA-c2c7-rcm5-vvqj
transitive, CVSS 7.5, fixed in 2.3.2
https://osv.dev/vulnerability/GHSA-c2c7-rcm5-vvqj - pnpm-lock.yamlprotobufjs 7.5.3 — GHSA-685m-2w69-288q
transitive, CVSS 7.5, fixed in 7.5.6
https://osv.dev/vulnerability/GHSA-685m-2w69-288q - pnpm-lock.yamlprotobufjs 7.5.3 — GHSA-jvwf-75h9-cwgg
transitive, CVSS 7.5, fixed in 7.5.6
https://osv.dev/vulnerability/GHSA-jvwf-75h9-cwgg - pnpm-lock.yamlprotobufjs 7.5.3 — GHSA-wcpc-wj8m-hjx6
transitive, CVSS 7.5, fixed in 7.6.1
https://osv.dev/vulnerability/GHSA-wcpc-wj8m-hjx6 - pnpm-lock.yamluuid 11.1.0 — GHSA-w5hq-g745-h8pq
transitive, CVSS 7.5, fixed in 11.1.1
https://osv.dev/vulnerability/GHSA-w5hq-g745-h8pq - pnpm-lock.yamluuid 9.0.1 — GHSA-w5hq-g745-h8pq
transitive, CVSS 7.5, fixed in 11.1.1
https://osv.dev/vulnerability/GHSA-w5hq-g745-h8pq - pnpm-lock.yaml@grpc/grpc-js 1.13.4 — GHSA-m9gg-hp2v-232j
transitive, CVSS 7.4, fixed in 1.13.6
https://osv.dev/vulnerability/GHSA-m9gg-hp2v-232j - pnpm-lock.yamlnanoid 3.3.11 — GHSA-xwg4-73v4-xw9w
transitive, CVSS 7.4, fixed in 3.3.12
https://osv.dev/vulnerability/GHSA-xwg4-73v4-xw9w - pnpm-lock.yamllodash 4.17.21 — GHSA-f23m-r3pf-42rh
transitive, CVSS 6.9, fixed in 4.18.0
https://osv.dev/vulnerability/GHSA-f23m-r3pf-42rh - pnpm-lock.yamlsprintf-js 1.0.3 — GHSA-hp3w-g68c-fv3c
transitive, CVSS 6.9
https://osv.dev/vulnerability/GHSA-hp3w-g68c-fv3c - pnpm-lock.yamlbrace-expansion 1.1.12 — GHSA-f886-m6hf-6m8v
transitive, CVSS 6.5, fixed in 1.1.13
https://osv.dev/vulnerability/GHSA-f886-m6hf-6m8v - pnpm-lock.yamlqs 6.14.0 — GHSA-4mjr-xmp4-gh2g
transitive, CVSS 6.3, fixed in 6.16.0
https://osv.dev/vulnerability/GHSA-4mjr-xmp4-gh2g - pnpm-lock.yamlqs 6.14.0 — GHSA-6rw7-vpxm-498p
transitive, CVSS 6.3, fixed in 6.14.1
https://osv.dev/vulnerability/GHSA-6rw7-vpxm-498p - pnpm-lock.yamlqs 6.14.0 — GHSA-q8mj-m7cp-5q26
transitive, CVSS 6.3, fixed in 6.15.2
https://osv.dev/vulnerability/GHSA-q8mj-m7cp-5q26
Maintenance
- recency
last commit 379 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
LICENSE present with no SPDX-License-Identifier tag; identified as 'MIT' from its text
- readme_quality
README.md: installation instructions (+25), 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
CHANGELOG.md present
- 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.