ai.law.mcp/lawyer-search
version 0.2.3
- scanned 2026-10-16
- source github.com/risk-ai/lawai-mcp-server
- commit 6267b2f510ac
- transport streamable-http
- files read 9
- methodology 0.2.0
- ruleset 0.1.1
No tag matching version 0.2.3 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
1 vendored or minified path was excluded before scanning; machine-generated bundles are not the server's own code
95
34
50measured on 45% of this axis
43
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
auth enforcement present at a call site in the source (auth middleware) 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.law.ai; 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 (MCP_API_KEYS, MCP_DB_PASSWORD, MCP_MASTER_KEY) and documented in the README
- authorization_granularity
14 tool registrations with conditional access logic present in the same source
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.json@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 - package-lock.jsonip-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 - package-lock.jsonfast-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 - package-lock.jsonfast-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 - package-lock.jsonfast-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 - package-lock.jsonfast-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 - package-lock.jsonfast-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 - package-lock.jsonfast-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 - package-lock.jsonfast-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 - package-lock.jsonfast-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 - package-lock.jsonhono 4.12.15 — GHSA-88fw-hqm2-52qc
transitive, CVSS 7.1, fixed in 4.12.25
https://osv.dev/vulnerability/GHSA-88fw-hqm2-52qc - package-lock.jsonhono 4.12.15 — GHSA-9vqf-7f2p-gf9v
transitive, CVSS 6.5, fixed in 4.12.16
https://osv.dev/vulnerability/GHSA-9vqf-7f2p-gf9v - package-lock.jsonhono 4.12.15 — GHSA-gqvv-2mrq-wpjv
transitive, CVSS 6.5, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-gqvv-2mrq-wpjv - package-lock.jsonhono 4.12.15 — GHSA-hvrm-45r6-mjfj
transitive, CVSS 6.5, fixed in 4.12.27
https://osv.dev/vulnerability/GHSA-hvrm-45r6-mjfj - package-lock.jsonhono 4.12.15 — GHSA-rv63-4mwf-qqc2
transitive, CVSS 6.5, fixed in 4.12.25
https://osv.dev/vulnerability/GHSA-rv63-4mwf-qqc2 - package-lock.jsonip-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 - package-lock.jsonip-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 - package-lock.jsonip-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 - package-lock.jsonqs 6.15.1 — 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.1 — GHSA-q8mj-m7cp-5q26
transitive, CVSS 6.3, fixed in 6.15.2
https://osv.dev/vulnerability/GHSA-q8mj-m7cp-5q26 - package-lock.jsonqs 6.15.1 — GHSA-x5fp-wj9c-mxmx
transitive, CVSS 6.3, fixed in 6.16.0
https://osv.dev/vulnerability/GHSA-x5fp-wj9c-mxmx - package-lock.jsonhono 4.12.15 — GHSA-w62v-xxxg-mg59
transitive, CVSS 6.1, fixed in 4.12.27
https://osv.dev/vulnerability/GHSA-w62v-xxxg-mg59 - package-lock.json@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 - package-lock.jsonhono 4.12.15 — GHSA-crvj-82cr-hjcx
transitive, CVSS 5.9, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-crvj-82cr-hjcx - package-lock.jsonhono 4.12.15 — GHSA-wwfh-h76j-fc44
transitive, CVSS 5.9, fixed in 4.12.25
https://osv.dev/vulnerability/GHSA-wwfh-h76j-fc44 - package-lock.jsonhono 4.12.15 — GHSA-2gcr-mfcq-wcc3
transitive, CVSS 5.3, fixed in 4.12.21
https://osv.dev/vulnerability/GHSA-2gcr-mfcq-wcc3 - package-lock.jsonhono 4.12.15 — GHSA-54fx-42gc-7vw4
transitive, CVSS 5.3, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-54fx-42gc-7vw4 - package-lock.jsonhono 4.12.15 — GHSA-8j4g-w8fx-2239
transitive, CVSS 5.3, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-8j4g-w8fx-2239 - package-lock.jsonhono 4.12.15 — GHSA-g6gw-c38x-mqfc
transitive, CVSS 5.3, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-g6gw-c38x-mqfc - package-lock.jsonhono 4.12.15 — GHSA-j6c9-x7qj-28xf
transitive, CVSS 5.3, fixed in 4.12.25
https://osv.dev/vulnerability/GHSA-j6c9-x7qj-28xf - package-lock.jsonhono 4.12.15 — GHSA-p77w-8qqv-26rm
transitive, CVSS 5.3, fixed in 4.12.18
https://osv.dev/vulnerability/GHSA-p77w-8qqv-26rm - package-lock.jsonhono 4.12.15 — GHSA-xrhx-7g5j-rcj5
transitive, CVSS 5.3, fixed in 4.12.21
https://osv.dev/vulnerability/GHSA-xrhx-7g5j-rcj5 - package-lock.jsonip-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 - package-lock.jsonfast-uri 3.1.0 — 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.15 — GHSA-f23p-vx2j-j53r
transitive, CVSS 4.8, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-f23p-vx2j-j53r - package-lock.jsonhono 4.12.15 — GHSA-f577-qrjj-4474
transitive, CVSS 4.8, fixed in 4.12.21
https://osv.dev/vulnerability/GHSA-f577-qrjj-4474 - package-lock.jsonhono 4.12.15 — GHSA-wgpf-jwqj-8h8p
transitive, CVSS 4.8, fixed in 4.12.25
https://osv.dev/vulnerability/GHSA-wgpf-jwqj-8h8p - package-lock.jsonhono 4.12.15 — GHSA-xgm2-5f3f-mvvc
transitive, CVSS 4.8, fixed in 4.12.27
https://osv.dev/vulnerability/GHSA-xgm2-5f3f-mvvc - package-lock.jsonhono 4.12.15 — GHSA-69xw-7hcm-h432
transitive, CVSS 4.7, fixed in 4.12.16
https://osv.dev/vulnerability/GHSA-69xw-7hcm-h432 - package-lock.jsonhono 4.12.15 — GHSA-hxh3-vqpv-xpqv
transitive, CVSS 4.7, fixed in 4.13.7
https://osv.dev/vulnerability/GHSA-hxh3-vqpv-xpqv - package-lock.jsonhono 4.12.15 — GHSA-3hrh-pfw6-9m5x
transitive, CVSS 4.3, fixed in 4.12.21
https://osv.dev/vulnerability/GHSA-3hrh-pfw6-9m5x - package-lock.jsonhono 4.12.15 — GHSA-qp7p-654g-cw7p
transitive, CVSS 4.3, fixed in 4.12.18
https://osv.dev/vulnerability/GHSA-qp7p-654g-cw7p - package-lock.jsonhono 4.12.15 — GHSA-hm8q-7f3q-5f36
transitive, CVSS 3.8, fixed in 4.12.18
https://osv.dev/vulnerability/GHSA-hm8q-7f3q-5f36 - package-lock.jsonbody-parser 2.2.2 — GHSA-v422-hmwv-36x6
transitive, CVSS 3.7, fixed in 2.3.0
https://osv.dev/vulnerability/GHSA-v422-hmwv-36x6 - package-lock.jsonhono 4.12.15 — GHSA-79qm-7rj5-m7r9
transitive, CVSS 3.7, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-79qm-7rj5-m7r9 - 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
Maintenance
- recency
last commit 140 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 (3 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), exposed tools or resources enumerated (+30), 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.