Monitoring and observability · MCP server
SolidPing: MCP server, setup and security
SolidPing is an open-source MCP server published on GitHub that lets an AI agent monitor uptime and manage incidents, maintenance windows and status pages. Its repository has 26 stars and its last commit is from October 24, 2026 and it is licensed under AGPL-3.0.
What SolidPing does
According to its repository: “Uptime monitoring over MCP. List and create checks, read incidents and results, manage maintenance windows and status pages. Self-hosted single Go binary, 40 check types, probes in several regions.”
The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. SolidPing is listed under Monitoring and observability, a category of 57 servers in the directory, where it ranks #28 by stars.
Topics declared by the repository: alerting, devops, distributed-systems, golang, health-check, incident-management.
Installing and connecting SolidPing
Distribution modes declared in the official MCP registry:
- remote server (streamable-http): you connect to it by URL, with nothing to install locally
It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: Go.
Security: what to check
Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.
None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to SolidPing. That does not replace reading the code.
Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.
Project activity and maintenance
Created on March 22, 2026, the fclairamb/solidping repository has 26 stars and 2 forks, with 2 open issues. It has more stars than 42% of the servers in the directory. It received changes this month. Version published in the registry: 0.41.0 (October 22, 2026).
Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.
Verdict
SolidPing is a reasonable choice; check the points below before connecting it.
Strengths
- Maintained by the service's own vendor
- Active project: recent commit
- Listed in the official MCP registry
- Usable remotely, without installation
Alternatives
- Netdata81.1K ★
- MCP grafana3.6K ★
- Openstatus9.2K ★
- OneUptime7.8K ★
- Homebutler305 ★
- Marmot Data Catalog623 ★
Learn more
Frequently asked questions
How do I install SolidPing?
SolidPing is distributed as a remote server. Add it to your client's MCP configuration (Claude Desktop, Cursor, VS Code…) following the README of fclairamb/solidping.
Is SolidPing free?
The code is published under the AGPL-3.0 licence and can be used free of charge.
Is SolidPing safe?
No risk signal found (system access, secrets, licence, abandonment). As with any MCP server, keep rights minimal and read the code before sensitive use.
Is it an official server?
Yes: the awesome-mcp-servers list marks it as the service vendor's official implementation.
What are the alternatives to SolidPing?
In the same category: Netdata, MCP grafana, Openstatus, and OneUptime. Netdata and MCP grafana score higher on our grid.
Related articles
- Build your own MCP server in 30 minutesOctober 24, 2026
- Automate your inbox with an AI agentOctober 18, 2026
- MCP, A2A, and tool calling: agent protocols explainedOctober 17, 2026
- Build an AI agent with n8n, without codingOctober 16, 2026
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score