betterstack
Server Details
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
- 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
9 toolsacknowledge_incidentAcknowledge an incidentIdempotentInspect
Acknowledge an ongoing incident, signalling that someone is looking into it (stops further escalation). Idempotent-ish: acknowledging an already-acknowledged incident returns HTTP 409. Uptime API: POST /api/v3/incidents/{id}/acknowledge.
| Name | Required | Description | Default |
|---|---|---|---|
| incident_id | Yes | The incident id to acknowledge (from list_incidents). | |
| acknowledged_by | Yes | User e-mail or a custom identifier of who is acknowledging the incident. |
get_incidentGet an incidentRead-onlyInspect
Get a single incident by id, including cause, status, timeline timestamps (started/acknowledged/resolved), who acknowledged/resolved it, and the related monitor. Uptime API: GET /api/v3/incidents/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| incident_id | Yes | The incident id (from list_incidents). |
get_monitorGet a monitorRead-onlyInspect
Get a single monitor by id, including current status, last_checked_at, SSL/HTTP settings, regions, and alerting configuration. Uptime API: GET /api/v2/monitors/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| monitor_id | Yes | The monitor id (from list_monitors). |
list_heartbeatsList heartbeatsRead-onlyInspect
List heartbeats (cron/background-job monitors that expect a periodic ping), with period, grace, and status (up/down/paused/pending). Uptime API: GET /api/v2/heartbeats.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number for pagination (default 1). | |
| per_page | No | Results per page. | |
| team_name | No | Filter by team name (only when using a global API token). |
list_incidentsList incidentsRead-onlyInspect
List incidents (alerts triggered by monitors/heartbeats), filterable by date range, monitor, and acknowledged/resolved state. Each incident carries cause, started_at, acknowledged_at, resolved_at. Uptime API: GET /api/v3/incidents.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | End date yyyy-mm-dd (inclusive). | |
| from | No | Start date yyyy-mm-dd (inclusive). | |
| page | No | Page number for pagination (default 1). | |
| per_page | No | Results per page. | |
| resolved | No | true = only resolved, false = only unresolved. | |
| team_name | No | Filter by team name (only when using a global API token). | |
| monitor_id | No | Only incidents for this monitor id. | |
| acknowledged | No | true = only acknowledged, false = only unacknowledged. | |
| heartbeat_id | No | Only incidents for this heartbeat id. |
list_monitorsList monitorsRead-onlyInspect
List uptime monitors with their status (up/down/paused/pending/maintenance/validating), check frequency, and alert settings. Good first call to discover what is being monitored. Uptime API: GET /api/v2/monitors.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Filter monitors by their monitored URL. | |
| page | No | Page number for pagination (default 1). | |
| per_page | No | Results per page. | |
| team_name | No | Filter by team name (only when using a global API token). | |
| pronounceable_name | No | Filter monitors by their pronounceable name. |
list_on_callList on-call schedulesRead-onlyInspect
List on-call calendars/schedules and the users currently on call for escalation. Useful to see who gets paged. Uptime API: GET /api/v2/on-calls.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number for pagination (default 1). | |
| per_page | No | Results per page. | |
| team_name | No | Filter by team name (only when using a global API token). |
list_status_pagesList status pagesRead-onlyInspect
List public/private status pages with company name, subdomain, aggregate_state, and published flag. Uptime API: GET /api/v2/status-pages.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number for pagination (default 1). | |
| per_page | No | Results per page. | |
| team_name | No | Filter by team name (only when using a global API token). |
resolve_incidentResolve an incidentIdempotentInspect
Resolve an ongoing incident, marking it as handled/closed. Idempotent-ish: resolving an already-resolved incident returns HTTP 409. Uptime API: POST /api/v3/incidents/{id}/resolve.
| Name | Required | Description | Default |
|---|---|---|---|
| incident_id | Yes | The incident id to resolve (from list_incidents). | |
| resolved_by | Yes | User e-mail or a custom identifier of who is resolving the incident. |
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!