SolidPing
OfficialSolidPing’s MCP server lets you operate uptime monitoring, incident triage, and public status pages.
Browse, filter, get, create, update, and delete monitoring checks.
Validate check configurations, list supported check types and sample configs, and discover available regions and check groups.
Run checks immediately and diagnose current health, recent results, and incidents for a check.
Query monitoring results and incidents, including timelines and notification attempts.
Probe targets without saving anything: run JavaScript checks, fetch URLs, or inspect pages with a headless browser.
Create, update, delete, and inspect status pages, sections, pinned resources, and customer-facing incident publications.
Read-only tools work with
mcp:read; write tools require themcpscope and an organization role.
Allows monitoring ClickHouse database connectivity and query execution as a check type.
Provides Discord notifications and SSO integration.
Allows monitoring Docker container health as a check type.
Provides GitHub SSO integration for authentication.
Provides GitLab SSO integration for authentication.
Provides Google SSO integration for authentication.
Sends notifications to Google Chat.
Allows monitoring Kubernetes cluster and API server health as a check type.
Allows monitoring MariaDB connectivity and query execution as a check type.
Sends notifications to Mattermost.
Allows monitoring MongoDB with ping command as a check type.
Allows monitoring MQTT broker connectivity as a check type.
Allows monitoring MySQL connectivity and query execution as a check type.
Sends notifications to ntfy.
Provides OpenTelemetry observability integration.
Sends notifications and escalates incidents to PagerDuty.
Allows monitoring PostgreSQL connectivity and query execution as a check type.
Allows monitoring Prometheus endpoints and metrics as a check type, and exposes /metrics.
Allows monitoring RabbitMQ broker connectivity as a check type.
Allows monitoring Redis with PING command as a check type.
Provides Sentry error tracking integration.
Provides Slack notifications and SSO integration.
Allows monitoring Source/Steam game servers via A2S query.
Allows monitoring Valve Source game servers via A2S protocol.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
SolidPing
Distributed, self-hostable uptime monitoring. 44 check types, multi-region workers, private agents, status pages, incidents and on-call escalation, in a single Go binary.
https://github.com/user-attachments/assets/fe207622-7957-4e85-8a3c-d33281799f4b
From docker run to the first result in 41 seconds, recorded from a real server with make showcase. The Tour page has the same cut if the player does not load.
Run it
docker run -p 4000:4000 --name solidping --hostname solidping -v solidping-data:/data ghcr.io/fclairamb/solidpingOpen http://localhost:4000 and sign in as admin@solidping.io with the password printed once at the first start:
docker logs solidping 2>&1 | grep "First login"Set SP_ADMIN_PASSWORD before the first start to choose it, or to recover a lost one while it has not been changed yet. You must pick a new password on first login: the account can do nothing else until then.
--hostnameis required: the worker name comes from it and must match^[a-z][a-z0-9-]{2,20}$(or setSP_NODE_NAME).Data (SQLite database and uploads) lives in
/data, so keep the volume.For production, use PostgreSQL: add
-e SP_DB_TYPE=postgres -e SP_DB_URL='postgresql://user:pass@host:5432/solidping'. Migrations run on first boot.
Every other setting is an SP_ environment variable, all optional: see the configuration docs.
Other ways to run it:
Hosted | www.solidping.io, no card needed |
Docker Compose | |
Binary (Linux, macOS, Windows) | |
Homebrew |
|
winget |
|
Scoop |
|
Kubernetes | |
Railway, Fly.io, Coolify, CasaOS, YunoHost |
Related MCP server: uptimepage
Screenshots
Checks list | New-check form | Check detail |
Check types
Check | Type | What it checks |
| Status codes, body, JSON and header assertions, timing breakdown | |
| Port connectivity, optional send/expect payload | |
| Port reachability, optional send/expect payload | |
| Ping | |
| Record resolution | |
| Connection handshake | |
| RDP negotiation, optional authenticated logon | |
| RFB handshake and authentication | |
| Broken links, mixed content, sitemap errors | |
| Health endpoint, reported per component | |
| Outages reported by a vendor's status page | |
| Certificate validity and expiration | |
| Domain expiration (WHOIS/RDAP) | |
| DNS blocklist membership | |
| Connection and query | |
| Connection and query | |
| Ping command | |
| PING command | |
| Connection and query | |
| Connection and query | |
| Connection and query | |
| Connectivity, STARTTLS, AUTH, optional real probe email | |
| Server availability | |
| Server availability | |
| A known message reaches an inbox (JMAP) | |
| Server availability | |
| Server availability | |
| Server availability | |
| Service health | |
| Broker connectivity | |
| Broker connectivity | |
| Broker connectivity | |
| VoIP server OPTIONS ping | |
| Reachability and clock drift | |
| Device monitoring | |
| Container health | |
| Workload replica health | |
| Source / Steam game server query | |
| Java and Bedrock server query | |
| xDSL/FTTH line quality | |
| Thresholds on a scraped metric | |
| Passive: alerts when pings stop (cron jobs, CI) | |
| Sandboxed scripts: multi-step API flows, logins, aggregation | |
| Headless Chrome: full render, screenshots |
Inspiration
Uptime Kuma: a self-hosted monitor that is easy to run (migration guide).
Better Stack: incidents, on-call escalation and status pages in one product (migration guide).
Gatus: checks defined as configuration (migration guide).
UptimeRobot: fast onboarding, one URL and you are monitoring (migration guide).
Healthchecks.io: heartbeat monitoring for cron jobs.
Checkly: scripted API and browser checks.
Contributing
Bug reports and pull requests are welcome. CONTRIBUTING.md covers local setup (make dev)
and PR conventions. Found a security issue? See SECURITY.md rather than opening a public issue.
License
AGPL-3.0 - See LICENSE.
Available Tools
23 toolscreate_checkCreate checkAInspect
Create a new monitoring check and return it (uid, slug, placement, resolved periods). If you don't know what config shape a given type expects, call list_check_types with type first to fetch a working starting config, then use validate_check to dry-run before creating. An enabled check starts running on its next tick and opens an incident after its confirmation period; pass enabled:false to create it paused. A duplicate slug is rejected with a conflict, never merged — use update_check to change an existing check. Counts against the organization's MaxChecks quota (an over-quota create is refused); reversible with delete_check. Requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.
Inputs: config (required), name, slug, type, +13 more. Returns: uid, name, slug, type, +12 more
create_status_pageCreate status pageAInspect
Create a status page and return it: uid, slug, name, visibility, default and enabled flags. A duplicate slug fails with a conflict. The first page of an organization becomes its default, and isDefault:true moves the default to the new page. A new page is enabled, public, and seeded with one "Services" section: add sections with manage_status_page_section and pin checks with manage_status_page_resource. Not quota-limited; reversible with delete_status_page. Use update_status_page instead to change an existing page. Requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.
Inputs: name (required), slug (required), language, customCss, +9 more. Returns: uid, name, slug, enabled, +4 more
delete_checkDelete checkADestructiveIdempotentInspect
Soft-delete one check, named by identifier (its UID or slug, as list_checks returns; an unknown one fails with not found and changes nothing). The check stops running immediately, its active incidents are resolved and its scheduling jobs removed; historical results are kept. A check that other checks tunnel through is refused. The deletion is permanent: there is no undelete, though it frees a slot in the MaxChecks quota. To stop a check without losing it, use update_check with enabled:false instead. Requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.
Inputs: identifier (required). Returns: deleted, identifier
delete_status_pageDelete status pageADestructiveIdempotentInspect
Soft-delete one status page, named by identifier (its UID or slug, as list_status_pages returns; an unknown one fails with not found and changes nothing). The page disappears from the API and the public site with its sections and resources, and its uploaded brand assets are deleted. Not quota-limited. There is no undelete (permanent, not reversible): use update_status_page with enabled:false to take a page down without destroying it, and manage_status_page_section or manage_status_page_resource with action=delete to remove part of a page. Requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.
Inputs: identifier (required). Returns: deleted, identifier
diagnose_checkDiagnose checkARead-onlyIdempotentInspect
Diagnose one check in a single call: its current status, its newest raw results per region, its active incident and its last resolved one. Use it instead of chaining list_results and list_incidents when someone asks "what's wrong with check X?"; use list_results for older history. identifier takes the UID or slug; recentResultsLimit (default 5, max 20) is per region, and the whole response holds at most 100 results, so it stays small and costs about one get_check plus one list_results. freshness and regionalIssue are omitted when there is nothing to report, and the incidents are null when there are none. Read-only: works with mcp:read tokens.
Inputs: identifier (required), recentResultsLimit. Returns: check, freshness, recentResults, regionalIssue, +2 more
get_checkGet checkARead-onlyIdempotentInspect
Get one check by identifier (its UID or its slug, e.g. "api-prod"); an unknown identifier fails with not found. Returns the check object only: type, config, regions, labels, group, period and status, with no result history. with=lastResult adds the most recent result and with=lastStatusChange the time the status last changed. Use diagnose_check for a triage briefing (recent results and incidents), list_results for history, and list_checks to search by name or label. Read-only: works with mcp:read tokens.
Inputs: identifier (required), with. Returns: uid, name, slug, type, +12 more
get_incidentGet incidentARead-onlyIdempotentInspect
Get one incident by UID (incidents have no slug); an unknown UID fails with "incident not found". Returns the incident: number, state, timestamps and failure counts. with=check adds its check and with=events up to 50 timeline events. include=notifications adds its notification attempts, newest first; status and limit filter only that list. Use list_incidents to search across incidents, and diagnose_check for a check's full triage briefing. Read-only: works with mcp:read tokens.
Inputs: uid (required), with, limit, status, +1 more. Returns: uid, kind, check, state, +12 more
get_status_pageGet status pageARead-onlyIdempotentInspect
Get one status page by identifier (UID or slug). with=sections embeds the sections and their resources in the page; include returns separate lists next to it instead, and include=resources needs sectionIdentifier to name the section. state and active filter only include=incidents. Use list_status_pages to browse every page, and manage_status_page_section / _resource / _incident to change them. Read-only: works with mcp:read tokens.
Inputs: identifier (required), with, state, active, +2 more. Returns: uid, name, slug, enabled, +7 more
list_check_groupsList check groupsARead-onlyIdempotentInspect
List every check group of the organization in one unpaginated response: slug, rolled-up status and check count per group. A group bundles related checks for shared incident handling and dashboard layout. Use it to find the checkGroupUid that create_check and update_check take, or the group a status page resource pins; use list_checks with checkGroupUid for the checks inside a group, and list_check_types for the kinds of check you can create. Groups are created and edited in the dashboard, not through MCP. Read-only: works with mcp:read tokens.
Inputs: no named parameters. Returns: data
list_checksList checksARead-onlyIdempotentInspect
List monitoring checks for the organization, optionally filtered by name/slug substring, labels, or check group; the filters combine with AND. Returns {data, pagination}. Use this for browsing or filtering a fleet of checks. To investigate a single check's current health, use diagnose_check instead; if you already know its UID or slug, get_check is more direct. Read-only: works with mcp:read tokens.
Inputs: q, with, limit, cursor, +2 more. Returns: data, pagination
list_check_typesList check typesARead-onlyIdempotentInspect
List all monitoring check types supported by this server (e.g. http, tcp, dns, icmp, ssl), or with type, the ready-made sample configs of that type. Call it without arguments first when you don't know what type to use: it returns {data: [...]}, one entry per type. Then call it with type=: it returns {data: [...]} with one entry per matching type carrying its samples, each a complete, valid config to clone and modify (much more reliable than guessing field names). Read-only: works with mcp:read tokens.
Inputs: type. Returns: data
list_incidentsList incidentsARead-onlyIdempotentInspect
List internal incidents (active or resolved) for the organization, newest first, up to 100 per page. checkUid, state, since and until combine with AND, and since/until bound the incident start time, so they also apply on top of a cursor. Use order=asc with the returned cursor to poll for new incidents: the cursor is then always returned and means strictly after (rows younger than 5 s are held back); changes to existing incidents are not listed again. Use diagnose_check for one check's incidents plus its current health, get_incident for one incident's timeline, and get_status_page include=incidents for the customer-facing entries. Read-only: works with mcp:read tokens.
Inputs: size, with, order, since, +4 more. Returns: data, pagination
list_regionsList regionsARead-onlyIdempotentInspect
List the monitoring regions this organization can run checks from, and its default placement set. Call it before create_check or update_check to pick the regions array; a check with no regions runs in defaultRegions. Use run_check to execute a check in its regions now, and list_results with region to read one region's history. Takes no parameters. Read-only: works with mcp:read tokens.
Inputs: no named parameters. Returns: data, defaultRegions
list_resultsList resultsARead-onlyIdempotentInspect
Query monitoring results for trend analysis or a specific time window. periodType picks the rows: raw returns single executions, hour, day and month return rollups, and the bucket-only with fields (availabilityPct, durationMinMs, durationMaxMs) apply to rollups only. All filters combine with AND. Pages hold 20 rows by default, 100 at most; pass pagination.cursor back as cursor for the next one, and read window and effectiveFilter to see what the server actually queried after defaulting. For one check's current state, use diagnose_check instead. Read-only: works with mcp:read tokens.
Inputs: size, with, cursor, region, +6 more. Returns: data, window, pagination, effectiveFilter
list_status_pagesList status pagesARead-onlyIdempotentInspect
List every status page of the organization, newest first, in one unpaginated response: each page's UID, slug, name, default flag, enabled flag and visibility, without its sections. Takes no parameters. Use get_status_page with the UID or slug for one page's sections, resources or published incidents. Read-only: works with mcp:read tokens.
Inputs: no named parameters. Returns: data
manage_status_page_incidentManage status page incidentADestructiveInspect
Manage the customer-facing incidents a status page shows (publications), distinct from the internal incidents list_incidents returns. Titles and bodies are shown to CUSTOMERS: never paste probe output, error strings, internal hostnames or IPs. action=create publishes a hand-written incident (pageIdentifier, title). action=update edits a publication's title, severity or state (pageIdentifier, publicationUid; PATCH semantics). action=add_update appends a narrative entry (pageIdentifier, publicationUid, kind, bodyMarkdown); entries are append-only. action=publish relays an EXISTING internal incident (incidentUid, pageIdentifier) with a title templated from the page. action=unpublish removes a relayed incident from the page (incidentUid, publicationUid), keeping the row for audit. create, add_update and publish notify status-page subscribers (hourly cap) and every action reaches webhook connections. Read publications with get_status_page include=incidents. Annotated destructive and non-idempotent because one of its actions removes data. Every action requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.
Inputs: action (required), kind, state, title, +5 more. Returns: uid, kind, stale, state, +13 more
manage_status_page_resourceManage status page resourceADestructiveInspect
Pin, edit or unpin a resource (a check or a check group) in a status page section. action=create pins exactly one of checkUid or checkGroupUid and returns the resource. action=update edits one (resourceUid required; omitted fields are kept). action=delete unpins it, returning {deleted, identifier}; the check or group itself is untouched. Read a section's resources with get_status_page include=resources. Annotated destructive and non-idempotent because one of its actions removes data. Every action requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.
Inputs: action (required), pageIdentifier (required), sectionIdentifier (required), checkUid, +5 more. Returns: uid, deleted, checkUid, position, +4 more
manage_status_page_sectionManage status page sectionADestructiveInspect
Create, update or delete a section of a status page. action=create adds a section (name and slug required); action=update edits one (sectionIdentifier required; omitted fields are kept); both return the section. action=delete permanently removes a section and every resource pinned in it, returning {deleted, identifier}. Read a page's sections with get_status_page include=sections. Annotated destructive and non-idempotent because one of its actions removes data. Every action requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.
Inputs: action (required), pageIdentifier (required), name, slug, +2 more. Returns: uid, name, slug, deleted, +3 more
probeProbe a targetARead-onlyIdempotentInspect
Explore a target and test a js check before create_check, without saving anything. kind=script runs a js check script exactly as a SolidPing worker would and returns status, output (with console) and metrics; env carries plaintext parameters and secrets only NAMES the secret parameters, which run empty. kind=fetch GETs a URL from the server. kind=browser snapshots a page to pick selectors for browser steps. kind selects the mode; the other params apply only to their kind (script: script/env/secrets/timeout; fetch and browser: url). Reaches the URL or script target you name. Read-only: works with mcp:read tokens.
Inputs: kind (required), env, url, script, +2 more. Returns: output, status, metrics, durationMs
run_checkRun check nowAInspect
Run a check once, now, in every region, instead of waiting for its next period (use it right after a fix, or on a freshly created check). The run goes through the normal result path: it can open or resolve an incident like any scheduled run. Rate limited per check and per organization. A region status of queued means due now, or right after the run in progress; read the outcome with diagnose_check or list_results (a result with periodStart >= requestedAt). Requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.
Inputs: identifier (required). Returns: regions, requestedAt
update_checkUpdate checkAIdempotentInspect
Update an existing check by UID or slug and return the updated check. PATCH semantics — only the fields you pass are modified, others stay as-is, except config, which is replaced whole rather than merged. Use create_check to make a new check and delete_check to remove one; to pause without deleting, set enabled:false instead. Modifies the check in place without consuming quota; reversible by updating again with the previous values. Requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.
Inputs: identifier (required), name, slug, config, +14 more. Returns: uid, name, slug, type, +12 more
update_status_pageUpdate status pageAIdempotentInspect
Update an existing status page by UID or slug and return the updated page. PATCH semantics — only fields you pass change, omitted fields keep their current values; the page must already exist and a slug that collides with another page is rejected. Use create_status_page to make a new page and delete_status_page to remove one instead. Modifies the page in place without consuming any quota, so it is reversible by updating again with the previous values. Requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.
Inputs: identifier (required), name, slug, enabled, +11 more. Returns: uid, name, slug, enabled, +4 more
validate_checkValidate checkARead-onlyIdempotentInspect
Dry-run validate a check config without creating or changing anything — a pure read, no side effects. valid is false exactly when fields lists the blocking findings (every one of them, not just the first), while warnings are advisory notes that never block. Use this before create_check when you've assembled a config from scratch or modified a sample, to catch problems early. Read-only: works with mcp:read tokens.
Inputs: type (required), config (required). Returns: valid, fields, warnings
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 23 tools
Each tool targets a distinct resource+action pair, and the descriptions actively cross-reference neighbours (get_check vs diagnose_check vs list_results, list_incidents vs manage_status_page_incident, probe vs run_check) so an agent can route correctly. The three manage_status_page_* tools are multi-action but clearly partitioned by sub-resource (section, resource, publication).
Nearly everything is snake_case verb_noun (list_checks, create_check, delete_status_page, get_incident), which is highly predictable. Minor deviations: the bare noun 'probe' breaks the verb_noun pattern, and the manage_status_page_* tools bundle create/update/delete behind an action parameter instead of using the separate create_/update_/delete_ convention used for checks and pages.
23 tools is on the heavy side, but the surface covers two real domains (checks and status pages) and the multi-action manage_* tools keep the count down. Every tool maps to a genuine operation; a few read-only listers (list_regions, list_check_groups, list_status_pages) could arguably be folded but they earn their place as pickers.
Checks have full lifecycle coverage (create/update/delete/get/list, validate, run, diagnose, results, types, regions, groups) and status pages have CRUD plus section/resource/incident management. Minor gaps: check groups are dashboard-only (read-only here), and internal incidents can be read but not created, acknowledged, or annotated through MCP.
Maintenance
Related MCP Connectors
MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents.
Pingstack monitors cron jobs and scheduled tasks with heartbeat checks, and checks websites, TCP ports, DNS records, SSL certificates and domain expiry. This MCP server lets your agent create, update, pause and delete checks, build dashboards and publish them as status pages, manage notification groups, and read incidents with their causes, uptime, run history and latency. Pause, delete and unpublish stay off until you turn them on. Browser sign-in, no API key needed.
Create, test, and manage uptime monitors for websites and APIs from your AI agent.
Uptime, SSL, DNS and domain monitoring you can talk to from Claude or any MCP client.
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceMCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents like Claude, ChatGPT, and Cursor.18 npmMIT
uptimepageofficial
AlicenseNot gradedqualityBmaintenanceMCP server for Uptimepage uptime monitoring. An LLM client can read your monitors and incidents, run a check on demand, and post incident updates. Writes need an OAuth login and a scoped token, and each one is logged.60AGPL 3.0- FlicenseNot gradedqualityCmaintenanceUptime, SSL, DNS and domain monitoring you can talk to: check, create and manage monitors for all your client sites from Claude, ChatGPT, or any MCP client.1-
- AlicenseNot gradedqualityDmaintenanceOfficial Hyperping MCP server for uptime, API, cron and server monitoring. 26 tools covering monitors, outages and timelines, uptime, response time, MTTR and MTTA, on-call schedules and escalation policies, over a remote Streamable HTTP endpoint with Bearer token auth and no install.1MIT