betterstack

Tools

9 tools: 7 read-only, 2 change data, 0 high risk (delete, pay, send or run code).

No tool name points to sending messages.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 1,764 tokens of tool definitions and a 612 ms handshake.

• changes dataacknowledge_incidentAcknowledge 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.
• changes dataresolve_incidentResolve 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.
• read-onlylist_monitorsList 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.
• read-onlyget_monitorGet 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}.
• read-onlylist_incidentsList 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.
• read-onlyget_incidentGet 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}.
• read-onlylist_heartbeatsList 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.
• read-onlylist_on_callList 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.
• read-onlylist_status_pagesList public/private status pages with company name, subdomain, aggregate_state, and published flag. Uptime API: GET /api/v2/status-pages.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-04, 612 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-052026-10-04

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Bookings and appointments, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/betterstack.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/betterstack.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=betterstack.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/betterstack.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/betterstack.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=betterstack.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.