fettle-mcp

MCPcommunity
v0.1.1sh.fettleUnknownUpdated 1d agonpmGitHub

Uptime monitoring for developers — monitors, incidents, heartbeats and status pages

Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1d agoLast update
Needs 1 credential before it runs
  • FETTLE_API_KEYAPI keyrequired

    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.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorsh.fettle
LicenseUnknown
Version0.1.1
Sourcenpm+mcp-registry
npmfettle-mcp
GitHubdarkweid/monitoring-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
F
10/100Untrusted
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
—CVE scan · not run+0/30
→ Not yet scanned — package must be on npm
—Static analysis · clean+0/20
→ Not yet scanned — package must be on npm
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scanNot runHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Not probed yet

Forge has not completed a tools/list handshake against this endpoint, so it holds no observation of what the server exposes. Nothing here says it exposes nothing.

About

Uptime monitoring for developers — monitors, incidents, heartbeats and status pages

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package has not been scanned yet, so no dependency tree has been resolved.