Developer · Remote MCP server
SolidPing
Self-hostable uptime monitoring: create checks, read incidents, manage status pages.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.fclairamb/solidping- Version
- 0.37.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- fclairamb (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/fclairamb) · how
- Website
- solidping.io
- Repository
- github.com/fclairamb/solidping
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://solidping.io/api/v1/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- solidping v0.38.0 · protocol 2025-06-18
- Tools discovered
- Not listed - auth_required: HTTP 401
- Checked on
- 2026-10-05
How to connect SolidPing
SolidPing is a remote MCP server: there is nothing to install. Its endpoint is https://solidping.io/api/v1/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Software DesignSOLID/OOP/DRY, the 23 GoF patterns, pattern scaffolding, and heuristic code-smell detection. | Local · stdio |
| SoftwareForgeAI-native Day 0 modernization platform for PRDs, architecture, work orders, and code transformation. | Remote · HTTPLive check: sign-in required |
| Solana Security StandardScan Solana/Anchor code against the Solana Security Standard and serve the ruleset to MCP clients. | Local · stdio |
| Solapur Software Developers RegistryPublic read-only MCP HTTP gateway for the Solapur software developers registry. | Remote · HTTPLive check: ✗ no handshake |
| Solitaire for AgentsIdentity infrastructure for AI agents. Evolving persona, session continuity, self-tuning retrieval. | Local · stdio |
| SolumbeDeterministic local repository context, impact analysis, and merge-readiness evidence for AI agents. | Local · stdio |
| Solvicus FinOps - GCP Committed Use Discount (CUD) OptimizationFinOps for Google Cloud: size 1- and 3-year CUD commitments to known demand. Also solves LP/MIP. | Remote · HTTPLive check: sign-in required |
| SomaRMCP runtime for provider-backed agents with CLI, REST, HTTP MCP, plugins, and scaffold support. | Local · stdio |