SolidPing
io.github.fclairambPublished by GitHub account fclairambv0.49.3Updated Nov 14, 2026
Self-hostable uptime monitoring: create checks, read incidents, manage status pages.
Overview
SolidPing MCP server for uptime monitoring: lets an assistant list checks and incidents, diagnose outages, validate and create checks, and manage status pages.
- What you can do
- List and inspect monitoring checks, their raw result history and available regions
- Diagnose why a check is failing and validate a check configuration before saving it
- Explore check types and sample configs, and probe a target or JavaScript script
- Create and manage checks, including the many protocol and service check types
- Manage status page sections, resources and incidents
- With extra toolsets enabled: maintenance windows and integrations
- When to use it
- Useful when you run SolidPing (hosted or self-hosted) and want an assistant to answer "what is down and why", review check history, or set up and adjust checks and status pages without clicking through the UI.
- Requirements
- A remote endpoint at solidping.io (streamable HTTP) and a SolidPing account; the assistant authenticates with an organization-scoped token. Writes to status pages, incidents, maintenance windows and integrations need a token with the mcp scope, since mcp:read tokens are read-only. Optional toolsets are enabled through the endpoint URL or an environment variable.
Installation
In SourceWeft
- Open SolidPing in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.fclairamb%2Fsolidping/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"solidping": {
"type": "http",
"url": "https://solidping.io/api/v1/mcp"
}
}
}README
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
Open http://localhost:4000 and sign in with [email protected] / solidpass.
You must pick a new password on first login: the pair is public, so 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:
Screenshots
Check types
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.
Source: README.md at commit 621d492
Tools
0Version history
25- v0.49.3LatestNov 14, 2026
- v0.49.2Nov 14, 2026
- v0.49.1Nov 13, 2026
- v0.49.0Nov 13, 2026
- v0.48.0Nov 12, 2026
- v0.47.0Nov 11, 2026
- v0.44.3Nov 7, 2026
- v0.44.2Nov 7, 2026
- v0.44.0Nov 6, 2026
- v0.43.1Nov 5, 2026
- v0.43.0Oct 31, 2026
- v0.42.1Oct 30, 2026
- v0.42.0Oct 29, 2026
- v0.41.0Oct 22, 2026
- v0.40.1Oct 19, 2026
- v0.40.0Oct 19, 2026
- v0.39.0Oct 18, 2026
- v0.38.6Oct 17, 2026
- v0.38.5Oct 14, 2026
- v0.38.3Oct 12, 2026
- v0.38.2Oct 11, 2026
- v0.38.1Oct 9, 2026
- v0.38.0Oct 5, 2026
- v0.37.0Oct 4, 2026
- v0.32.1Sep 25, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts