cronitor
Server Details
Manage Cronitor monitors and send telemetry pings — list, inspect, create, update, delete.
- 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
6 toolscronitor_create_monitorCreate monitorDestructiveInspect
Creates a monitor in Cronitor (additive). Cronitor API: POST /monitors. Sends only the fields you provide.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Unique monitor id/key. | |
| name | No | Human-readable monitor name. | |
| note | No | Free-form note stored on the monitor. | |
| tags | No | Tags to group/filter monitors. | |
| type | Yes | Monitor type: job | check | heartbeat | site. | |
| notify | No | Notification list names to alert. | |
| request | No | For type=check: {url, method?, headers?, body?, ...}. | |
| schedule | No | Cron expression (job) or interval string, e.g. '0 9 * * *' or 'every 5 minutes'. | |
| assertions | No | Assertions, e.g. "response.code = 200". |
cronitor_delete_monitorDelete monitorDestructiveInspect
PERMANENTLY deletes a monitor from Cronitor. Destructive and irreversible. Cronitor API: DELETE /monitors/{key}.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Monitor key/id to delete. |
cronitor_get_monitorGet monitorRead-onlyInspect
Get full detail for one monitor (latest_event, latest_invocations, passing status) — the 'is X healthy right now?' tool. Cronitor API: GET /monitors/{key}.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Monitor key/id (unique identifier). |
cronitor_list_monitorsList monitorsRead-onlyInspect
List monitors and their current passing/failing status. Cronitor API: GET /monitors (paginated via page + pageSize).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-based). Default 1. | |
| pageSize | No | Monitors per page. |
cronitor_ping_monitorPing monitor (telemetry)DestructiveInspect
Reports a telemetry event (run/complete/fail/ok/pause) for a monitor — records job/heartbeat activity and can clear or trigger alerts. Cronitor telemetry: GET {telemetryUrl}/p/{apiKey}/{monitorKey}?state=...
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Monitor key/id to ping. | |
| host | No | Optional host identifier. | |
| state | Yes | Telemetry state: run | complete | fail | ok | pause. | |
| metric | No | Optional metric, e.g. "count:1" or "duration:30". | |
| series | No | Optional series id to correlate run/complete pings. | |
| message | No | Optional message attached to the event. |
cronitor_update_monitorUpdate monitorDestructiveInspect
Creates or updates a monitor by key (e.g. change schedule, pause via paused:true). Cronitor API: PUT /monitors with a single monitor object. Sends only the fields you provide.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Monitor key/id to create or update. | |
| name | No | Human-readable monitor name. | |
| note | No | Free-form note stored on the monitor. | |
| tags | No | Tags to group/filter monitors. | |
| type | No | Monitor type: job | check | heartbeat | site. | |
| notify | No | Notification list names to alert. | |
| paused | No | Set true to pause the monitor, false to resume. | |
| request | No | For type=check: {url, method?, headers?, body?, ...}. | |
| schedule | No | Cron expression (job) or interval string, e.g. '0 9 * * *' or 'every 5 minutes'. | |
| assertions | No | Assertions, e.g. "response.code = 200". |
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!