Skip to main content
Glama

Server Details

Know when cron jobs and AI agents stop running: create monitors and check in from your agent.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

B3.2/5.0

Scored across 37 tools

Disambiguation4/5

Most tools map to a distinct resource+action pair across pages, monitors, channels, pixels, teams, runs and events. A few pairs need the description to separate: list_events vs list_monitor_events, and make_page_private vs share_page/update_page, which all touch page visibility. delete_monitor vs pause_monitor is clearly explained, so boundaries hold.

Naming Consistency4/5

Overwhelmingly consistent snake_case verb_noun (create_monitor, list_runs, delete_team, update_channel). Minor deviations: make_page_private uses a three-part verb phrase and check_in is verb+particle rather than verb_noun. Team membership uses add_team_member/remove_team_member, a different but still readable pattern.

Tool Count3/5

37 tools is heavy for one server, though the surface spans six distinct sub-domains (pages, monitors, channels, pixels, teams, runs/events), so many tools are earned. Still, several are near-siblings (get_page/list_pages, get_monitor/list_monitors, get_pixel/list_pixels) that push it past a comfortable size. Borderline rather than clearly scoped.

Completeness3/5

Monitors, pages, channels and teams have solid lifecycle coverage, but pixels lack any update operation and channels lack a get_channel (list-only). Reads are also thin in places: runs and events are list/get only with no per-run filtering beyond a monitor, and there is no way to update account-level settings.

Available Tools

37 tools
add_team_memberAdd team memberA
Idempotent
Inspect

Add the account of a person with a Vivere login to a team. Joining a team that has pages takes a seat.

Inputs: email (required), team_id (required).

check_inCheck inAInspect

Report on a heartbeat monitor: 'success' after a completed run (resets the deadline), 'start' when a run begins, 'fail' when it failed. Include a short message; it is kept as the run log.

Inputs: monitor_id (required), items, model, status, +6 more.

create_channelCreate alert channelAInspect

Add an alert channel. Settings by kind: email {to}; webhook {url, secret}; slack {url}; discord {url}; telegram {token, chat_id}; ntfy {url, token}.

Inputs: kind (required), name (required), config (required).

create_monitorCreate monitorAInspect

Create a heartbeat monitor (default) or an HTTP check on the account's first page or on page_id, which may be a page shared with this account as editor. Returns the monitor and, for heartbeats, the ping URL to call after each run.

Inputs: name (required), url, cron, kind, +6 more.

create_pageCreate pageAInspect

Add a page to group monitors under, within the account's limit on pages. Its slug is its public address, made from the title when not given.

Inputs: title (required), slug.

create_pixelCreate pixelAInspect

Make a tracking pixel, within the account's limit on pixels. Returns the tag to paste into a page or an email.

Inputs: name (required).

create_teamCreate teamCInspect

Make a team.

Inputs: name (required).

delete_channelDelete alert channelA
DestructiveIdempotent
Inspect

Delete an alert channel. Monitors stop sending alerts to it.

Inputs: channel_id (required).

delete_monitorDelete monitorA
DestructiveIdempotent
Inspect

Delete a monitor and all its history. This cannot be undone; pause_monitor stops alerts without losing anything.

Inputs: id (required).

delete_pageDelete pageA
DestructiveIdempotent
Inspect

Delete one of your pages. Only an empty page that is not your first can go.

Inputs: page_id (required).

delete_pixelDelete pixelA
DestructiveIdempotent
Inspect

Delete a pixel and every load it recorded.

Inputs: pixel_id (required).

delete_teamDelete teamA
DestructiveIdempotent
Inspect

Delete a team. Its members lose the pages it gave them.

Inputs: team_id (required).

get_accountGet accountA
Read-onlyIdempotent
Inspect

Which account this key belongs to, its limits and what it uses of them, and what this key may do: its permission on each resource (none, read or write) and the pages it is limited to, if any.

Inputs: no named parameters.

get_monitorGet monitorA
Read-onlyIdempotent
Inspect

Get one monitor by id, including its ping URL for heartbeat monitors, or by page_id and slug, which also works on a page shared to view.

Inputs: id, slug, page_id.

get_pageGet pageA
Read-onlyIdempotent
Inspect

One page: its public address, monitors and, on your own pages, who it is shared with and as what.

Inputs: page_id (required).

get_pixelGet pixelB
Read-onlyIdempotent
Inspect

One pixel and its newest loads: when, from which page, browser, language and platform.

Inputs: pixel_id (required), limit.

get_runGet runB
Read-onlyIdempotent
Inspect

One run with the output it sent (the log), where it came from and what it cost.

Inputs: run_id (required).

get_teamGet teamB
Read-onlyIdempotent
Inspect

One team: its members and the pages shared with it.

Inputs: team_id (required).

list_channelsList alert channelsA
Read-onlyIdempotent
Inspect

Your alert channels. Secret settings are never shown; secrets_set names the ones that have a value.

Inputs: no named parameters.

list_eventsList eventsC
Read-onlyIdempotent
Inspect

Status changes across the account's own monitors, newest first.

Inputs: limit.

list_monitor_eventsList monitor eventsA
Read-onlyIdempotent
Inspect

One monitor's status changes (up, down, late, paused), newest first.

Inputs: id (required), limit.

list_monitorsList monitorsA
Read-onlyIdempotent
Inspect

List the monitors on every page this account can see, or on one page, with status, page and access. Monitors on a page shared to view have no id; address them by page_id and slug.

Inputs: tag, query, page_id.

list_pagesList pagesA
Read-onlyIdempotent
Inspect

List the pages this account can see: its own, then pages other accounts share with it, each with the access it has there (owner, editor or viewer) and how many monitors are on it and down.

Inputs: no named parameters.

list_pixelsList pixelsB
Read-onlyIdempotent
Inspect

Your tracking pixels, with the tag to paste and how often each has loaded.

Inputs: no named parameters.

list_runsList runsA
Read-onlyIdempotent
Inspect

A heartbeat monitor's newest runs with their outcome, duration, exit code and any model, tokens and cost they reported, plus what its runs cost over 30 days.

Inputs: id (required), limit.

list_teamsList teamsB
Read-onlyIdempotent
Inspect

Your teams, with how many members and pages each has.

Inputs: no named parameters.

make_page_privateMake page privateA
Idempotent
Inspect

Turn off Public on every monitor on one of your pages, which takes its public status page down.

Inputs: page_id (required).

pause_monitorPause monitorA
Idempotent
Inspect

Pause a monitor so it stops alerting until resumed or pinged again.

Inputs: id (required).

remove_team_memberRemove team memberC
Idempotent
Inspect

Take an account out of a team.

Inputs: team_id (required), account_id (required).

rename_teamRename teamC
Idempotent
Inspect

Rename a team.

Inputs: name (required), team_id (required).

resume_monitorResume monitorA
Idempotent
Inspect

Resume a paused monitor.

Inputs: id (required).

share_pageShare pageA
Idempotent
Inspect

Share one of your pages with the account of a person who has a Vivere login (email) or with one of your teams (team_id), as viewer or editor, or change the role they have. Needs a free seat for anybody new.

Inputs: role (required), page_id (required), email, team_id.

test_channelTest alert channelBInspect

Send a test alert to a channel.

Inputs: channel_id (required).

unshare_pageUnshare pageA
Idempotent
Inspect

Stop sharing one of your pages with an account (account_id, from get_page) or a team (team_id). Their alert channels come off its monitors.

Inputs: page_id (required), team_id, account_id.

update_channelUpdate alert channelB
Idempotent
Inspect

Rename a channel or change its settings. Settings left out keep their value.

Inputs: channel_id (required), name, config.

update_monitorUpdate monitorA
Idempotent
Inspect

Change a monitor. Only the fields given change; its kind cannot. Setting cron switches a heartbeat to a cron schedule and setting period switches it back. Only the page's owner can move it, with page_id, to another of their own pages.

Inputs: id (required), url, cron, name, +15 more.

update_pageUpdate pageA
Idempotent
Inspect

Rename one of your pages or change its slug, which moves its public address.

Inputs: page_id (required), slug, title.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to set up and manage uptime checks for websites and APIs, status pages, cron heartbeats, Lighthouse and SEO audits, alerts, and related monitoring tasks through AI apps.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      The watchdog for unattended AI agents: flags MISSED, FAILED, NO_EVIDENCE, RETRY_STORM, BUDGET, DRIFT and STALLED runs of Claude Code routines, OpenClaw, n8n and cron jobs, and alerts via Telegram, Slack or webhook. MIT and self-hostable.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to create monitors for cron jobs, webhooks, backups and scheduled GitHub Actions workflows, import a crontab after previewing proposed monitors, send start/success/failure check-ins with exit codes, and read monitor states, latest check-ins and the public status page. Fleet-wide instrumentation is possible with a single setup key, and alerts go out by e-mail or webhook when a routine fails or stops reporting.
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources