Placeholder. No logo or screenshot has been supplied for this listing yet.

Do you maintain this server? Claim this listing to add a logo or screenshot and to correct or extend it. Free, and a person checks every claim.

What it does

Uptime monitoring — monitors, incidents, heartbeats, maintenance windows, status page incidents

Description as published by the publisher in the official MCP Registry, read 14 Nov 2026. Not written or verified by Few Servers.

Facts

Registry name	`sh.fettle/mcp`
Publisher	fettle.sh Namespace verified by the registry through the publisher's domain.
Category	Monitoring and observability sorted by our keyword rules
Transport	remote (streamable-http), local package (npm)
Version	1.8.0
This version published	13 Nov 2026
Last seen	14 Nov 2026, in our crawl of the official MCP Registry
Tested by Few Servers	No

Remote endpoint (streamable-http), as published: https://api.fettle.sh/mcp
npm package, as published: fettle-mcp · version 1.5.0 · transport stdio
```
npx -y fettle-mcp
```
Standard run command for npm packages. The registry publishes the package name, not a command; check the repository for required arguments.

Install details read from the registry record on 11 Nov 2026. We have not run this server.

Needs a key or token: the registry record marks a secret value as required. Declared by the publisher:

Authorization (header, secret, not marked required): Optional: a Fettle API key as a bearer token, "Bearer fettle_…". Leave it out to sign in with OAuth in the browser instead.
FETTLE_API_KEY (environment variable, secret, required): Fettle API key (Settings → API Keys at https://fettle.sh). Read scope lists and inspects; write scope is needed to create, change or pause anything.
FETTLE_API_URL (environment variable, not marked required): Base URL of the Fettle API. Only set this to point the server at something other than production.
FETTLE_TIMEOUT_MS (environment variable, not marked required): How long one tool call may take before it is abandoned.

Being listed is not a safety check. Read the repository and check what a server asks for before you connect it. How the directory works.

No reviews yet.