app.evlek/mcp-server
version 3.1.4
- scanned 2026-10-16
- source github.com/Evlek/evlek-mcp
- commit fa46bf5754e3
- transport streamable-http
- files read 3
- methodology 0.2.0
- ruleset 0.1.1
95
89measured on 45% of this axis
44
93measured on 45% of this axis
91measured on 80% of this axis
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/index.js:81mcp-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 controller = new AbortController(); const timer = setTimeout(() => controller.abort(), REQUEST_TIMEOUT_MS); const res = await fetch(DATA_API, { method: 'POST', headers: { 'Content-Type': 'application/json' },
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://evlek.app/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
no committed credential found, and no environment variable with a credential-shaped name is read anywhere in the source
- authorization_granularity
no tool registration was recognised anywhere in the source. An MCP server registers tools by definition, so this is a gap in our detection rather than a server with none, and `03` §4's threshold cannot be applied to it. A tool-list handler IS present, so the tools are built in a shape this counter could not enumerate.
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.30.0 — GHSA-6qxp-vccf-f47h
direct, CVSS 7.5, fixed in 1.31.0
https://osv.dev/vulnerability/GHSA-6qxp-vccf-f47h - package-lock.jsonfast-uri 3.1.4 — 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.4 — 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.4 — 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.4 — 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.4 — 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.4 — GHSA-qw65-cvwx-89v3
transitive, CVSS 7.5, fixed in 3.1.7
https://osv.dev/vulnerability/GHSA-qw65-cvwx-89v3 - package-lock.jsonip-address 10.3.1 — GHSA-2vr4-cq9g-pvrc
transitive, CVSS 6.9, fixed in 10.5.1
https://osv.dev/vulnerability/GHSA-2vr4-cq9g-pvrc - package-lock.jsonhono 4.12.32 — GHSA-gqvv-2mrq-wpjv
transitive, CVSS 6.5, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-gqvv-2mrq-wpjv - package-lock.jsonip-address 10.3.1 — 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.3.1 — 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.3.1 — 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.jsonhono 4.12.32 — 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.32 — 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.32 — 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.32 — GHSA-g6gw-c38x-mqfc
transitive, CVSS 5.3, fixed in 4.13.5
https://osv.dev/vulnerability/GHSA-g6gw-c38x-mqfc - package-lock.jsonfast-uri 3.1.4 — 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.32 — 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.32 — 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.32 — GHSA-79qm-7rj5-m7r9
transitive, CVSS 3.7, fixed in 4.12.34
https://osv.dev/vulnerability/GHSA-79qm-7rj5-m7r9
Maintenance
- recency
last commit 3 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
a release exists but fewer than two fall inside `03` §5's 12-month window, so no median gap can be taken — and §5's remaining bands are all defined on that median. A limit of the methodology, not of this repository.
- bus_factor
2 regular authors in the last 12 months
- 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
specific scope or access documentation is present, but `03` §7's 100 and 60 bands both compare it against scopes INFERRED from static analysis, which is not built yet. Scoring 100 on an empty inference would be a vacuous truth — 'all ∅ inferred scopes are documented'.
- changelog
CHANGELOG.md present
- security_contact
no SECURITY.md, but README.md documents a disclosure route — `03` §7 accepts either
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.