# SolidPing

SolidPing's MCP server hands a coding agent the uptime side of a project: create checks, read incidents, manage status pages without leaving the chat.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 26
- Author: fclairamb
- License: AGPL-3.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/fclairamb/solidping
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/mcp/solidping

## What it does

SolidPing is uptime monitoring you host yourself, shipped as one Go binary. It covers 44 check types, from HTTP and DNS through Postgres, Kafka and a headless browser, and it handles incidents, on-call rotations and public status pages. The MCP server exposes that to an agent, so a check gets created or an incident gets read from the chat instead of the dashboard.

Transport is HTTP, so the client side installs nothing locally. Claude Code takes one command; Cursor and GitHub Copilot get the same endpoint as a JSON entry in their MCP servers block.

The monitor itself starts with `docker run -p 4000:4000 --hostname solidping ghcr.io/fclairamb/solidping`. SQLite is the default store and no second service is required. First login is `admin@solidping.io` with `solidpass`, and the panel will not let you keep that password — change it on the spot. Source is AGPL-3.0.

## Requirements
- Needs: Docker
- Remote server: `https://solidping.io/api/v1/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http solidping https://solidping.io/api/v1/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add solidping --url https://solidping.io/api/v1/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "solidping": {
            "url": "https://solidping.io/api/v1/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "solidping": {
            "type": "http",
            "url": "https://solidping.io/api/v1/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http solidping https://solidping.io/api/v1/mcp
```

## When to use it
- create an HTTP check from a URL without opening the dashboard
- list what is still failing after an outage
- publish a resource on a public status page
- read response-time history for one endpoint
- build an on-call schedule with escalation steps

## Example prompts
- Add a SolidPing check for the `/health` endpoint on staging, every minute.
- Which incidents are still open from the last hour?
- Put a new section for our API checks on the status page.

## Similar
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [Oh My Posh Validator](https://affpapa.org/en/nevibecode/mcp/oh-my-posh-validator.md) — MCP server · ★ 23643
- [Keploy](https://affpapa.org/en/nevibecode/mcp/keploy.md) — MCP server · ★ 18727
- [Coder](https://affpapa.org/en/nevibecode/mcp/coder.md) — MCP server · ★ 17160
- [mcp](https://affpapa.org/en/nevibecode/mcp/kubeshark-mcp.md) — MCP server · ★ 12109

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md