Grades are a hygiene check, not a security guarantee.

MCP, MCP server

Mcp Server

TestingBot's official Model Context Protocol (MCP) server implementation.

Compatibility: Not stated.

Grade C

One Medium finding. Read the report before installing.

Graded by PlugVetRubric v2

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

SECRETS_PATH_CREDENTIAL

Why this grade

  • SECRETS_PATH_CREDENTIAL Medium

    Mentions a credential store path (~/.ssh, id_rsa, .npmrc, .aws/credentials, credentials.json, .netrc).

    src/lib/credentials.ts, line 127 // same UNIX convention as ~/.aws/credentials and ~/.ssh. Returns the file path.

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

    src/lib/app-automate-client.ts, line 385

    const response = await fetch(`${APP_AUTOMATE_URL}${endpoint}`, {

    src/lib/app-automate-client.ts, line 406

    const response = await fetch(`${APP_AUTOMATE_URL}${endpoint}`, {

    src/tools/auth.ts, line 209

    const res = await fetch(`${baseUrl()}/mcp/oauth/device/code`, {

    Show more

    src/tools/logs.ts, line 20

    const response = await fetch(url, { signal });

    docs/device-auth-plan.md, line 190

    @redis ||= Redis.new(url: ENV.fetch("REDIS_URL", "redis://localhost:6379/1"))

    docs/device-auth-plan.md, line 301

    const codeRes = await fetch(`${BASE}/mcp/oauth/device/code`, {

    docs/device-auth-plan.md, line 356

    const res = await fetch(`${BASE}/mcp/oauth/device/token`, {

  • Secrets

    Concern

    reads a credential or environment file.

    SECRETS_ENV_READ SECRETS_PATH_CREDENTIAL SECRETS_PATH_DOTENV

    src/config.ts, line 9

    process.env.TESTINGBOT_KEY || process.env.TB_KEY || process.env.TESTINGBOT_USERNAME || "";

    src/config.ts, line 11

    process.env.TESTINGBOT_SECRET ||

    src/lib/credentials.ts, line 127

    // same UNIX convention as ~/.aws/credentials and ~/.ssh. Returns the file path.

    Show more

    src/config.ts, line 12

    process.env.TB_SECRET ||

    src/config.ts, line 13

    process.env.TESTINGBOT_ACCESS_KEY ||

    src/tools/project.ts, line 394

    " key: process.env.TESTINGBOT_KEY!,",

    src/tools/project.ts, line 395

    " secret: process.env.TESTINGBOT_SECRET!,",

    src/tools/project.ts, line 414

    " .usingServer(`https://${process.env.TESTINGBOT_KEY}:${process.env.TESTINGBOT_SECRET}@hub.testingbot.com/wd/hub`)",

    src/tools/project.ts, line 430

    " user: process.env.TESTINGBOT_KEY,",

    .gitignore, line 7

    # Environment variables

    .gitignore, line 8

    .env

    CONTRIBUTING.md, line 21

    cp .env.example .env # optional: fill in TESTINGBOT_KEY / TESTINGBOT_SECRET for live runs

    README.md, line 97

    Or create a `.env` file in your project:

    README.md, line 696

    cp .env.example .env

    README.md, line 697

    # Edit .env with your credentials

    docs/device-auth-plan.md, line 405

    INI-style with a single `[default]` profile for now. Future profiles (e.g. team accounts) just add another `[name]` block. The file is mode `0600` and lives in a `0700` directory -

  • Agent instructions

    Pass

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

  • Obfuscation

    Note

    a file was over the read cap and was not fully read.

    OBFUSCATION_FILE_OVER_READ_CAP

    package-lock.json, line 1

    {

  • Licence

    Pass

    A licence file is present (LICENSE).

  • Maintainer activity

    Pass

    The latest commit is within the last 365 days.

Get the full report on this tool, £49

Note

Hygiene check of commit 9927faa26513. can reach a host that is not written as a fixed address. reads a credential or environment file. a file was over the read cap and was not fully read.

Date and source

Date checked:

View source

github.com

Commit graded: 9927faa2651328374f1a8438be023ebde57e53d1

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