Bragproof

← Reports

fettle-mcp

Needs setup before it starts1.9.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: FETTLE_API_KEY
Contacts while installing and starting: nothing

0hosts contacted
0files written
95dependencies

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 fettle-mcp@1.9.1

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

Its error output names these settings: FETTLE_API_KEY.

What it said when it did not start
fettle-mcp: FETTLE_API_KEY is not set. Create an API key under API keys in the dashboard sidebar (https://dashboard.fettle.sh/api-keys) and add it to the fettle-mcp entry of your MCP client configuration, e.g. "env": { "FETTLE_API_KEY": "fettle_…" }.

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

Install facts

LicenseMIT
Needsnode >=20.0.0
Sourcegithub.com/fettlesh/monitoring-mcp
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-zV3vfrJvP7DBzLWbC/BUQkwme0Fh1nsgAqclsW3hgrWyxM8zbCW8wBXrOpvfQhRZ2mlSI36ZBS9e/8UzWkXpbw==

Versions reported

VersionRunResultTools
1.9.12026-11-16Needs setup before it starts0
1.6.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/fettle-mcp.svg)](https://bragproof.smaverk.com/r/fettle-mcp)

New version out? Ask for a fresh report.