healthchecksio
Server Details
Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
12 toolshealthchecksio_create_checkCreate checkDestructiveInspect
CREATES a new check — this MODIFIES live monitoring config. Provide a timeout (simple period-based check) OR a schedule + tz (cron-based check); the two are mutually exclusive. Use unique to avoid creating duplicates. Assign notifications via channels. Healthchecks: POST /checks/. Returns the created check (201) or the existing match (200).
| Name | Required | Description | Default |
|---|---|---|---|
| tz | No | Server's timezone for the cron `schedule`, e.g. "Europe/Riga". | |
| desc | No | Free-form description of the check. | |
| name | No | Human-readable name for the check. | |
| slug | No | URL slug (used for slug-based ping URLs). | |
| tags | No | Space-separated list of tags, e.g. "prod db backups". | |
| grace | No | Grace time in seconds after the deadline before the check goes down. | |
| unique | No | Dedupe fields — if a check already matches on these (e.g. ["name"]), it is returned instead of created. | |
| methods | No | Allowed ping HTTP methods: "" (any) or "POST" (POST-only). | |
| timeout | No | Expected period between pings, in seconds (60..31536000). Mutually exclusive with `schedule`. | |
| channels | No | Integrations to assign: "*" for all, or a comma-separated list of integration ids. | |
| schedule | No | Cron expression for the expected ping schedule (e.g. "15 5 * * *"). Mutually exclusive with `timeout`; requires `tz`. | |
| manual_resume | No | If true, a paused check does not auto-resume on the next ping (resume manually). |
healthchecksio_delete_checkDelete checkDestructiveInspect
PERMANENTLY DELETES a check by UUID — this MODIFIES live monitoring config and cannot be undone. Healthchecks: DELETE /checks/{uuid}. Returns the deleted check's last known state.
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | The check's UUID to delete. |
healthchecksio_get_checkGet checkRead-onlyInspect
Get a single check by its UUID (or its unique read-only key). Returns the check's full state — status, timeout/schedule, grace, tags, last ping. Healthchecks: GET /checks/{uuid}.
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | The check's UUID, or its unique read-only key. |
healthchecksio_get_ping_bodyGet ping bodyRead-onlyInspect
Get the logged request body of a single ping, returned as PLAIN TEXT (verbatim, not JSON). Healthchecks: GET /checks/{uuid}/pings/{n}/body.
| Name | Required | Description | Default |
|---|---|---|---|
| n | Yes | The ping's sequence number (the `n` field from list_pings). | |
| uuid | Yes | The check's UUID. |
healthchecksio_list_badgesList badgesRead-onlyInspect
List the project's status-badge URLs per tag (plus "*" for the overall status) — {badges:{...}}. Healthchecks: GET /badges/.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
healthchecksio_list_checksList checksRead-onlyInspect
List all checks in the project, optionally filtered by slug and/or tags. Returns {checks:[...]} — each check's status, schedule, last ping, and ping URL. Healthchecks: GET /checks/.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Filter to checks carrying ALL of these tags (each is sent as a separate `tag` query param). | |
| slug | No | Filter to checks with this exact slug. |
healthchecksio_list_flipsList flipsRead-onlyInspect
List a check's status changes ("flips") over time — [{timestamp, up}]. Optionally scope by a lookback window or an explicit start/end range. Healthchecks: GET /checks/{uuid}/flips/.
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | Return only flips at/before this Unix timestamp. | |
| uuid | Yes | The check's UUID. | |
| start | No | Return only flips at/after this Unix timestamp. | |
| seconds | No | Return only flips from the last N seconds. |
healthchecksio_list_integrationsList integrationsRead-onlyInspect
List the project's notification integrations ("channels") — {channels:[{id, name, kind}]}. The ids are what you assign to a check's channels field. Healthchecks: GET /channels/.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
healthchecksio_list_pingsList pingsRead-onlyInspect
List a check's logged pings (100 on the free plan, 1000 on paid), most recent first. Each ping: type, date, n, scheme, remote_addr, method, ua, rid, duration, body_url. Healthchecks: GET /checks/{uuid}/pings/.
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | The check's UUID. |
healthchecksio_pause_checkPause checkDestructiveInspect
PAUSES a check — disables monitoring without deleting it (it stops going down for missed pings until it next receives a ping or is resumed). This MODIFIES live monitoring config. Healthchecks: POST /checks/{uuid}/pause (empty body).
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | The check's UUID to pause. |
healthchecksio_resume_checkResume checkDestructiveInspect
RESUMES a paused check — re-enables monitoring. This MODIFIES live monitoring config. Returns HTTP 409 (surfaced cleanly) if the check is not currently paused. Healthchecks: POST /checks/{uuid}/resume (empty body).
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | The check's UUID to resume. |
healthchecksio_update_checkUpdate checkDestructiveInspect
UPDATES an existing check by UUID — this MODIFIES live monitoring config. Send only the fields you want to change (timeout and schedule remain mutually exclusive). Healthchecks: POST /checks/{uuid}. Returns the updated check.
| Name | Required | Description | Default |
|---|---|---|---|
| tz | No | Server's timezone for the cron `schedule`, e.g. "Europe/Riga". | |
| desc | No | Free-form description of the check. | |
| name | No | Human-readable name for the check. | |
| slug | No | URL slug (used for slug-based ping URLs). | |
| tags | No | Space-separated list of tags, e.g. "prod db backups". | |
| uuid | Yes | The check's UUID to update. | |
| grace | No | Grace time in seconds after the deadline before the check goes down. | |
| unique | No | Dedupe fields — if a check already matches on these (e.g. ["name"]), it is returned instead of created. | |
| methods | No | Allowed ping HTTP methods: "" (any) or "POST" (POST-only). | |
| timeout | No | Expected period between pings, in seconds (60..31536000). Mutually exclusive with `schedule`. | |
| channels | No | Integrations to assign: "*" for all, or a comma-separated list of integration ids. | |
| schedule | No | Cron expression for the expected ping schedule (e.g. "15 5 * * *"). Mutually exclusive with `timeout`; requires `tz`. | |
| manual_resume | No | If true, a paused check does not auto-resume on the next ping (resume manually). |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!