Grades are a hygiene check, not a security guarantee.

MCP, MCP server

io.github.Developyn/laver-mcp

An MCP server for Laver.

Compatibility: Not stated.

Grade B

Minor issues only, no Medium or High. Worth a quick look at the findings below before installing.

Graded by PlugVetRubric v2

Not a guarantee. A hygiene check of the source at the commit shown, not a security audit.

Rescanned at commit 6993f0181656, unchanged since the check below.

NETWORK_NO_FIXED_HOST SECRETS_PATH_DOTENV SECRETS_ENV_READ

Why this grade

  • NETWORK_NO_FIXED_HOST Low

    Makes a network call whose host is not written as a fixed address.

    server.js, line 171 response = await fetch(url, {

  • SECRETS_PATH_DOTENV Low

    Mentions a .env file.

    server.js, line 38 // That file is now `.env`, which holds `LAVER_API_KEY=…` alongside other

  • SECRETS_ENV_READ Note

    Reads an environment variable whose name contains KEY, SECRET, TOKEN, PASSWORD or CREDENTIAL.

    server.js, line 60 const path = process.env.LAVER_API_KEY_FILE;

Any High, or two or more Medium findings, give D. One Medium gives C. Low findings or a security Note give B. Each code names a finding behind the letter.

Grades are a hygiene check of the source at the commit shown, on the date checked, not a security audit or a guarantee. The free directory grades are automated. Before release, a PlugVet engineer reviews every paid report and any grade we hold back, including all F grades, against the source code and the evidence we quote.

What was checked

Plain notes from the hygiene checks.

  • Permissions

    Pass

    No shell or command execution found, and no extra permission was declared.

  • Install and update

    Pass

    No install-time script found, and dependencies are pinned or absent.

  • Network

    Concern

    can reach a host that is not written as a fixed address.

    NETWORK_NO_FIXED_HOST

    server.js, line 171

    response = await fetch(url, {

  • Secrets

    Concern

    reads a credential or environment file.

    SECRETS_ENV_READ SECRETS_PATH_DOTENV

    server.js, line 38

    // That file is now `.env`, which holds `LAVER_API_KEY=…` alongside other

    server.js, line 48

    // what it points at changed underneath it - `.env` now, and the briefing tells

    server.js, line 60

    const path = process.env.LAVER_API_KEY_FILE;

    Show more

    server.js, line 49

    // agents to copy `backend/.env` (database credentials, signing secrets) into

    server.js, line 105

    const API_KEY = process.env.LAVER_API_KEY || key_from_file();

    README.md, line 31

    file containing nothing but the key, or a `.env`-style file with a

    README.md, line 46

    project, reading the key from the gitignored `.env`. Nothing to export.

    README.md, line 542

    LAVER_API_KEY_FILE=../.env node check.js --live-api

    README.md, line 558

    `node_modules`, its `.env`, and the Postgres they point at. No API key and no

    README.md, line 563

    It is only as local as `backend/.env` is, though. Running it **writes to

  • Agent instructions

    Pass

    No instruction to ignore earlier instructions or to hide a step.

  • Obfuscation

    Pass

    No encoded or minified payload found.

  • Licence

    Pass

    A licence file is present (LICENSE).

  • Maintainer activity

    Pass

    The latest commit is within the last 365 days.

Note

Hygiene check of commit 6993f0181656. can reach a host that is not written as a fixed address. reads a credential or environment file.

Date and source

Date checked:

View source

github.com

Commit graded: 6993f0181656ffb7603650971382ca8858180173

This link goes to the original host. PlugVet does not host or check what you download from there, and installing it is your own decision and risk.

Read how this letter is chosen