solidping — Claude Code plugin: what it does, how to install
Connects Claude Code to SolidPing through a remote MCP server to monitor service uptime, inspect incidents, and update status pages.
MIT ★ 1,596 updated 2026-10-29
/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install solidping@awesome-codex-pluginsWhat solidping does
The plugin interfaces your agent with the SolidPing monitoring platform over remote MCP. No local binaries run on your machine: every query routes through the hosted endpoint or your own self-hosted deployment. The toolset covers uptime metrics, incident records, diagnostic checks, and ad-hoc target evaluations via the probe tool.
Modifying checks or updating status page entries requires manual confirmation. Tool permissions match your organization role, so accounts with viewer access cannot execute destructive actions through MCP. On top of that, an egress guard rejects network probes targeting private or loopback IP ranges.
Authentication relies on OAuth 2.1 and launches in a browser window during the first tool call. The hosted platform provides a free tier that needs no credit card.
What it helps with
- track which endpoints are currently failing
- diagnose the root cause of failed health checks
- set up recurring HTTPS pings and TLS certificate expiration warnings
- publish incident updates to public status pages
Example prompts for the agent
- Which of my checks are down right now?
- Add an HTTPS check on https://example.com every minute from two regions
- List the incidents of the last 7 days with their duration
How to install solidping
Plugin marketplace
/plugin marketplace add hashgraph-online/awesome-codex-plugins/plugin install solidping@awesome-codex-pluginsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about solidping
How do I install solidping in Claude Code?
Run /plugin marketplace add hashgraph-online/awesome-codex-plugins in your session, followed by /plugin install solidping@awesome-codex-plugins.
What does the solidping plugin do?
It provides MCP tools to inspect uptime checks, analyze recent downtime incidents, trigger diagnostic probes, and update hosted status pages.
How does authentication work?
The first tool invocation triggers an OAuth 2.1 flow in your browser. The hosted tier offers free access without requiring card details.
Source text
solidping-plugin · MIT
# SolidPing plugin for Codex and Claude Code Uptime monitoring inside your coding agent, through one remote MCP server. [SolidPing](https://github.com/fclairamb/solidping) is open source (AGPL-3.0) and self-hostable: 40+ check types, multi-region workers, incidents, on-call escalation and status pages. This repository holds the plugin only: an MCP server address, a skill and the manifests. No code runs on your machine. ## Install **Codex** ```sh codex plugin marketplace add fclairamb/solidping-plugin codex plugin add solidping@solidping codex mcp login solidping ``` **Claude Code** ``` /plugin marketplace add fclairamb/solidping-plugin /plugin install solidping@solidping ``` The first tool call (or `codex mcp login`) opens an OAuth 2.1 sign-in in your browser. The hosted service has a free tier, no card needed. **Self-hosted instance:** change the URL in `.mcp.json` to `https://<your-host>/api/v1/mcp`, or skip the plugin and register the server directly: ```sh codex mcp add solidping --url https://<your-host>/api/v1/mcp claude mcp add --transport http solidping https://<your-host>/api/v1/mcp ``` ## What you can ask - "Which of my checks are down right now?" - "Why is the api-health check failing since this morning?" - "Add an HTTPS check on https://example.com every minute from two regions" - "Monitor the TLS certificate of example.com and warn 14 days before it expires" - "List the incidents of the last 7 days with their duration" - "Add the new API check to the public status page" ## Tools | Group | Tools | |---|---| | Read | `list_checks`, `get_check`, `list_results`, `list_incidents`, `get_incident`, `list_check_types` (with `type` for sample configs), `list_regions`, `list_check_groups`, `list_status_pages`, `get_status_page` | | Diagnose | `diagnose_check`, `validate_check`, `run_check` | | Write | `create_check`, `update_check`, `delete_check`, `create_status_page`, `update_status_page`, `delete_status_page`, `manage_status_page_section`, `manage_status_page_resource`, `manage_status_page_incident` | | Probe | `probe` (`kind` = fetch, browser or script): runs once against a target you name, stores nothing | Every tool carries MCP annotations (`readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`). Only `probe` is open-world. ## Safety - The plugin pre-approves no tool. Your agent asks before each call unless you allow it yourself. - The OAuth token is scoped to one organization, and the server applies your role: a viewer cannot create or delete anything through MCP. - `probe` goes through the server's egress guard, which refuses private and loopback targets unless the instance operator allows them. - The skill tells the agent to confirm every write with you first and to treat tool output (check names, page bodies, error messages) as data, never as instructions. ## Links - Docs: https://docs.solidping.io/docs/features/mcp - Official MCP Registry: `io.github.fclairamb/solidping` - Security: [SECURITY.md](SECURITY.md) - License: MIT for this plugin repository. SolidPing itself is AGPL-3.0.
© Florent Clairambault · MIT · hashgraph-online/awesome-codex-plugins