Bragproof

← Reports

bayze-mcp

Needs setup before it starts1.4.1npm

It exited or refused to answer until it is given configuration, such as a key or an argument. Run 2026-11-16.

Needs to start: BAYZE_API_KEY
Contacts while installing and starting: nothing

0hosts contacted
0files written
115dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y bayze-mcp@1.4.1

Installing a package runs its code. Use a sandbox for anything you have not read.

Its error output names these settings: BAYZE_API_KEY.

What it said when it did not start
bayze <command> [options]

commands:
  config check [--config <path>] [--strict]   validate config (read-only)
  config path                                 print the default config path
  run --workflow <id> [options]               execute a workflow (dev/acceptance tool)
  mcp [--config <path>] [--no-journal]        start the MCP stdio server (for AI clients)
  init [--dir <dir>]                          interactive setup wizard (generates config + .env)
  journal path                                print the default journal path
  journal clear                               delete the journal file
  journal tail [n]                            show the last n run summaries (default 20)
  eval --workflow <id> --tasks <path>         run evaluation tasks through a workflow
       [--compare <id>] [--config <path>]
       [--no-journal]
  models                                      list Bayze API models (needs BAYZE_API_KEY)
  balance [--config <path>]                   query Bayze API points balance

run options:
  --config <path>     config file (default: OS user config dir)
  --input <text|->    task input ('-' or omitted: read stdin)
  --no-journal        do not write the run summary journal
  --max-cost <usd>    tighten max cost (overrides may only tighten)
  --max-steps <n>     tighten max steps
  --timeout <ms>      tighten total timeout

mcp options:
  --config <path>     config file (default: OS user config dir)
  --no-journal        do not write run summaries

Written by the package or by npm, not by this site.

Install facts

LicenseMIT
Needsnode >=22
Sourcegithub.com/caijianxiong2007-prog/bayze-mcp
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-j536h1lBF+lH5oLvhCVXkxtmnKjvdZRiRPDcihMWuEjN08zbl+Kkkm30OzFPvw7bdnWVCOP/KClv9AVGUbIQqQ==

Versions reported

VersionRunResultTools
1.4.12026-11-16Needs setup before it starts0
1.0.02026-11-12Needs setup before it starts0

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Needs setup before it starts

[![Bragproof](https://bragproof.smaverk.com/badge/bayze-mcp.svg)](https://bragproof.smaverk.com/r/bayze-mcp)

New version out? Ask for a fresh report.