Fettle

by fettle.sh MCP server in Observability & incidents, indexed and not reviewed

HostedLocalvendor's ownwidely used

Not reviewed

No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.

How the index works

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

What the official MCP registry says

Facts

MCP registry
sh.fettle/mcp · 1.9.2
Endpoint
https://api.fettle.sh/mcp
Packages
npm fettle-mcp stdio
npm / week
1.7k
GitHub stars
0
Registry entry
updated 17 Nov 2026

From the official MCP registry, the package registries and our own checks. JSON · Markdown

Why it's listed

  • It's published in the registry under fettle.sh, a namespace the registry only gives to whoever proves they control that domain.
  • It's in real use: 1,665 npm downloads a week.

Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.

Tools it lists 57 · about 53,891 tokens of context · checked 19 hours ago

ToolWhat it doesHint
list_monitorsList monitorsFind monitors in the organization by name, target, type, status or tag. Each row is short: id, name, type, target, status, is_active, tags, interval_seconds, ssl_expires_at and last_checked_at. Use it first to get a…read-only
list_tagsList tagsList the tags used in the organization, most-used first, each with monitor_count and heartbeat_count, as items. Call it before tagging anything so you reuse an existing name instead of inventing a near-duplicate. Not a…read-only
get_monitorGet a monitorRead one monitor's full configuration and current state. It has type, target, interval_seconds, timeout_seconds, regions, config, status, is_active, confirmation_threshold, channel_ids (empty means every working channel…read-only
create_monitorCreate a monitorCreate one monitor that checks a URL, host or port on a schedule from one or more regions, and return it in the get_monitor shape. Use check_target first to catch a typo or an unreachable host; use bulk_create_monitors…writes
bulk_create_monitorsCreate several monitorsCreate 1 to 100 monitors in one call, all or nothing; for a single monitor use create_monitor. Requires a key with the write scope. An invalid item, or a batch that would exceed the plan, rejects the whole call and…writes
bulk_pause_monitorsPause many monitorsPause up to 100 monitors in one call, all or nothing: no checks run and each open incident closes without an alert. Use it to stop monitoring a whole project or group found with list_monitors; for one monitor use…writes
bulk_resume_monitorsResume many monitorsResume up to 100 paused monitors in one call, all or nothing; each goes back to PENDING and is checked on the next tick. For one monitor use resume_monitor; to run a check right away on a monitor that is already…writes
bulk_update_monitorsChange settings of many monitorsSet the same interval, timeout, regions, channels or threshold on up to 100 monitors in one call, all or nothing. For example, move twenty PING monitors to other regions. Not for config or name (use update_monitor, one…writes
get_exposed_ports_presetGet the exposed-ports presetList the ports that should never be reachable from the internet (databases, queues, admin panels). Returns ports, each a port number and the service that usually listens on it. Use it to pick ports when asked to watch a…read-only
update_monitorUpdate a monitorChange one monitor's settings and return it in the get_monitor shape. Only the fields you pass change, and at least one besides monitor_id is required (422 otherwise); type and target never change (create a new monitor…writes
pause_monitorPause a monitorStop checking one monitor without deleting it: its status becomes PAUSED and an open incident on it closes without a recovery alert. Use it when the user wants a monitor off for an open-ended time. For a planned deploy…writes
resume_monitorResume a monitorRestart checks on one paused monitor: its status goes back to PENDING and it is checked on the scheduler's next tick. For many monitors use bulk_resume_monitors; to check a running monitor right away use check_now.…writes
delete_monitorDelete a monitorDelete one monitor: it stops being checked and disappears from the organization's monitors, and no tool restores it. Use it only when the user explicitly asked for deletion; otherwise prefer pause_monitor, which keeps…writes
check_nowCheck a monitor nowQueue one existing monitor to run on the scheduler's next tick instead of waiting out its interval, for example to confirm a fix. It returns the monitor record, not a check result: call get_monitor or list_check_results…writes
bulk_update_monitor_tagsRetag several monitors at onceAdd and/or remove tags across up to 300 monitors in one call, all or nothing: each monitor ends with (its tags | add) - remove. Use it to retag a fleet; for heartbeats use bulk_update_heartbeat_tags, to replace one…writes
get_uptime_summaryGet uptime for a monitorReport one monitor's uptime percentage, average response time and incident count over the last 24 hours, 7 days and 30 days at once, to answer how reliable it has been. For a day-by-day series use get_uptime_daily; for…read-only
get_plan_usageGet plan usageShow the organization's plan, its limits and current usage, to check that new monitors, heartbeats or regions fit before creating them or to explain a 403 naming a limit. Region codes and their cities come from…read-only
list_incidentsList incidentsList the organization's monitor and heartbeat incidents, newest first (or by attention with sort), to see what is or was down and which alerts went out. Each item has id, monitor_id or heartbeat_id (exactly one is set),…read-only
acknowledge_incidentAcknowledge an incidentMark an open incident as being handled so its repeat alerts stop; the recovery alert still goes out when it resolves. Use it when someone is working on the outage. It does not close the incident (that happens when the…writes
list_heartbeatsList heartbeat monitorsFind heartbeat (cron / dead-man's-switch) monitors. Each has id, name, state (PENDING until a success ping makes it UP or a /fail ping makes it DOWN; later UP, DOWN or PAUSED), period_seconds, grace_seconds, ping_url,…read-only
create_heartbeatCreate a heartbeat monitorCreate a heartbeat: Fettle alerts when a scheduled job stops calling its ping_url. Use it for cron jobs, backups and workers that should report in; to probe a URL, host or port from outside use create_monitor. The job…writes
get_heartbeatGet a heartbeat monitorRead one heartbeat in full, including how long its last run took. It has name, state, period_seconds, grace_seconds, ping_url, last_ping_at, last_success_at, last_start_at, last_duration_ms (how long the last run took,…read-only
get_heartbeat_uptimeGet a heartbeat's uptimeReport one heartbeat's uptime over the last N days or a date range, in total and per UTC day, to answer how reliable a job has been. Uptime is the share of time since the heartbeat was created that no incident was open;…read-only
update_heartbeatUpdate a heartbeat monitorChange one heartbeat's name, timing, channels or tags; only the fields you pass change. A new period or grace moves the current deadline (overdue_at) at once, counted from the last ping; a heartbeat with no running…writes
bulk_update_heartbeat_tagsRetag several heartbeats at onceAdd and/or remove tags across up to 300 heartbeats in one call, all or nothing: each heartbeat ends with (its tags | add) - remove. Use it to retag many jobs; for monitors use bulk_update_monitor_tags, to replace one…writes
pause_heartbeatPause a heartbeat monitorPause one heartbeat: it is no longer reported late, pings to its ping_url are accepted but ignored, and its open incident closes without an alert. Use it when the job is stopped on purpose, such as a runner taken out of…writes
resume_heartbeatResume a heartbeat monitorResume one paused heartbeat: it goes back to PENDING with no deadline, so it is not reported late until its next success ping restarts the clock. Use it once the job runs again; to change its timing use…writes
delete_heartbeatDelete a heartbeat monitorDelete one heartbeat for good: its ping_url stops working (404) and no tool restores it. Use it only when the user asked for deletion; to stop alerts for a while use pause_heartbeat. Requires a key with the write scope.…writes
list_maintenance_windowsList maintenance windowsList every maintenance window of the organization, enabled or not, in effect or not. Each has id, name, enabled, scope (ORG or MONITOR), dtstart, duration_minutes, rrule, timezone, monitor_ids, created_at and…read-only
list_active_maintenanceList maintenance windows in effect nowList the enabled maintenance windows in effect at this moment, to tell whether a monitor's alerts are silenced now. An ORG-scope window covers every monitor, a MONITOR-scope one its monitor_ids. For every window,…read-only
get_maintenance_windowGet a maintenance windowRead one maintenance window with its schedule and its next three occurrences. It has the list_maintenance_windows fields plus next_occurrences, each with start and end. Use it to confirm when a recurring window fires…read-only
create_maintenance_windowCreate a maintenance windowCreate a one-time or recurring maintenance window that silences new alerts for some or all monitors. While a window is in effect its monitors keep being checked, but no incident opens and no down or change alert goes…writes
update_maintenance_windowUpdate a maintenance windowChange one maintenance window's name, schedule, scope or monitors, or switch it off with enabled false; only the fields you pass change. While a window is in effect its monitors keep being checked, but no incident opens…writes
delete_maintenance_windowDelete a maintenance windowDelete one maintenance window; alerts for its monitors resume at once and no tool restores it. To suspend a window but keep it, use update_maintenance_window with enabled false. Requires a key with the write scope.…writes
preview_maintenance_windowPreview a maintenance scheduleCompute the next three occurrences, each with start and end, that a schedule would produce, without saving anything. Use it to check a recurring schedule before create_maintenance_window or update_maintenance_window;…read-only
list_status_pagesList status pagesList the organization's public status pages. Each has id, slug, name, description, is_published (publicly visible now), history_days, telegram_publish_enabled (incident alerts in the org's Telegram chats offer a draft…read-only
list_check_resultsList a monitor's check resultsList one monitor's individual check results, newest first, to find out why it is DOWN: which regions fail and with what status code or error. Each has id, region, checked_at, status, response_time_ms, status_code,…read-only
list_changesList what changed on monitorsList confirmed changes to what monitors observe on their targets, newest first. Recorded today: DNS_ANSWERS from DNS monitors and CERTIFICATE from SSL monitors; REDIRECT and RESPONSE_HEADER are reserved for HTTP…read-only
get_response_time_by_regionGet a monitor's response time by regionChart one monitor's average response time over time, one series per region, to see where it is slow and since when. Returns monitor_id, window, bucket_seconds, regions and slowdown. Each region has region, display_name,…read-only
get_uptime_dailyGet a monitor's daily uptimeReport one monitor's uptime for each UTC day, oldest first and ending today, to find the day an outage or degradation began. Each day has date, uptime_percentage, downtime_seconds, observed_seconds, degraded_seconds,…read-only
get_incidentGet an incidentRead one incident in full, with every alert sent for it. It has id, monitor_id or heartbeat_id (exactly one is set), started_at, created_at, resolved_at, cause, cause_detail, last_notified_at, acknowledged_at,…read-only
get_incident_contextGet an incident's contextRead everything around one incident beyond its row: who acknowledged it, how each region's checks went, the latest checks, a per-region timeline and the downtime periods. Use it to tell an outage seen everywhere from…read-only
get_incident_diagnosisDiagnose an incidentRead what changed around a monitor incident, computed from the checks Fettle already holds. Start here for a DOWN monitor's open incident (its id from list_incidents with monitor_id and status "open") or a pasted alert,…read-only
rename_tagRename a tag everywhereRename a tag on every monitor and heartbeat that carries it; an item that already has the new name keeps one copy. Use it to fix a naming scheme across the organization; to change the tags of chosen monitors only use…writes
delete_tagRemove a tag everywhereRemove a tag from every monitor and heartbeat that carries it; the items themselves stay, and no tool restores the tag. Use it to retire a tag across the organization; to take it off chosen monitors only use…writes
get_status_pageGet a status pageRead one status page with its components. It has the list_status_pages fields, where each component has id, monitor_id, display_name and position. Use it to get the component ids that create_status_page_incident takes…read-only
list_status_page_incidentsList a status page's incidentsList the incidents shown on one status page, newest first, both posted by a person and opened by Fettle. Each has id, title, status, is_auto (opened by Fettle from a monitor), started_at, resolved_at, notified_at (when…read-only
draft_status_page_postDraft a status page postWrite the text of the page's next incident post from the monitor outages affecting it. It only drafts: nothing is posted and no subscriber is emailed. Show the draft to the user and post it with…read-only
create_status_page_incidentPost an incident on a status pageOpen a new incident on a status page with its first message, to tell the page's visitors about an outage. It is public and emails the page's confirmed subscribers: confirm the wording with the user before calling. Any…writes
post_status_page_updatePost an update to a status page incidentAdd a message to an existing status page incident and set its status; RESOLVED closes it. It is public and emails the page's confirmed subscribers: confirm the wording with the user before calling. Every confirmed…writes
update_status_page_incidentRename a status page incidentChange a status page incident's title without telling anyone: nothing is sent to subscribers. To change its status or add a message use post_status_page_update. Requires a key with the write scope. Returns the incident.…writes
delete_status_page_incidentDelete a status page incidentRemove an incident and its timeline from a status page; it stops showing at once, nothing is sent to subscribers, and no tool restores it. Use it for an incident posted by mistake; to close a real one use…writes
list_channelsList notification channelsList the organization's notification channels, to get the ids that channel_ids of monitors and heartbeats take: every member's own email channel, then up to 100 others (added email addresses first). Each has id, type,…read-only
list_regionsList check regionsList every check region of the platform, to show the user where checks can run. Returns regions, each with code (what a regions argument takes), display_name, city, country_code, group and group_display_name. The…read-only
check_targetProbe a target before creating a monitorRun one real check of a target from one region chosen by Fettle, without creating anything. It reports status (up, down, error or unknown), region, response_time_ms, status_code, error and failure_kind. unknown means no…read-only
record_deployMark a deployRecord that a deploy happened: the commit or tag (ref), when it finished (deployed_at) and which monitors it touched (monitor_ids, or tag + tag_match). Fettle stores it so that verify_deploy shows it and a later…writes
verify_deployCompare monitors before and after a deployCompare monitors before and after a deploy, without running any check. For each monitor it compares the checks since `since` with the 24 hours before it, per region, and returns verdict PASS, REGRESSED (most regions…read-only

What https://api.fettle.sh/mcp answered to tools/list, asked without credentials. answered without the initialize handshake. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.

How its tools read to an agent 0 errors · 20 warnings · 1 note

  • warnTC07get_incidentthe description is about 519 tokens
  • warnTC07get_incident_contextthe description is about 644 tokens
  • warnTC07get_incident_diagnosisthe description is about 816 tokens
  • warnTC07list_changesthe description is about 823 tokens
  • warnTC13bulk_create_monitorsmonitors[].config (object with no properties)
  • warnTC13check_targetconfig (object with no properties)
  • warnTC13create_monitorconfig (object with no properties)
  • warnTC13update_monitorconfig (object with no properties)
  • warnTC18verify_deployreadOnlyHint is true but the name says "deploy"
  • warnTC21bulk_update_monitor_tagsdescribed almost the same as bulk_update_heartbeat_tags (89% of the same words)
  • warnTC22check_nowthe definition is about 1,530 tokens
  • warnTC22create_monitorthe definition is about 3,391 tokens
  • warnTC22get_incident_contextthe definition is about 1,909 tokens
  • warnTC22get_incident_diagnosisthe definition is about 2,478 tokens
  • warnTC22get_monitorthe definition is about 1,779 tokens
  • warnTC22list_changesthe definition is about 1,717 tokens
  • warnTC22list_incidentsthe definition is about 1,760 tokens
  • warnTC22update_monitorthe definition is about 3,180 tokens
  • warnTC22verify_deploythe definition is about 2,768 tokens
  • warnTC23server57 tools, about 53,979 tokens of definitions
  • noteTC24server4 of 57 tools have no outputSchema

The checks from /check and anchor check, run each day on the list above: about 53,891 tokens of definitions. Not part of the score yet. Check your own server.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.