Remote MCP · Endpoint
com.seoapi/petalbot MCP server
Yes, as of 2 hours ago: the check failed for an unclassified reason.
DownLast checked 2 hours ago
Server URL
https://petalbot.seoapi.com/mcp
The last check failed: the check failed for an unclassified reason.
- Registry name
- com.seoapi/petalbot
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 22.2% from 18 checks
- Described by its publisher as
- Validate whether an IP address belongs to PetalBot. Remote MCP server exposing a validate_ip tool.
- Website
- https://seoapi.com/petalbot/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Failed - the check failed for an unclassified reason | — |
| 1 day ago | Failed - the check failed for an unclassified reason | — |
| 2 days ago | Handshake completed | 55 ms |
| 3 days ago | Failed - the check failed for an unclassified reason | — |
| 4 days ago | Failed - the check failed for an unclassified reason | — |
| 5 days ago | Failed - the check failed for an unclassified reason | — |
| 7 days ago | Failed - the check failed for an unclassified reason | — |
| 9 days ago | Handshake completed | 205 ms |
| 12 days ago | Failed - the check failed for an unclassified reason | — |
| 14 days ago | Handshake completed | 376 ms |
| 16 days ago | Failed - the check failed for an unclassified reason | — |
| 18 days ago | Failed - the check failed for an unclassified reason | — |
| 20 days ago | Failed - the check failed for an unclassified reason | — |
| 22 days ago | Failed - the check failed for an unclassified reason | — |
| 24 days ago | Failed - the check failed for an unclassified reason | — |
| 26 days ago | Failed - the check failed for an unclassified reason | — |
| 27 days ago | Failed - the check failed for an unclassified reason | — |
| 29 days ago | Handshake completed | 277 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 8 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with com.seoapi/petalbot and makes no claim about it beyond what these checks measured.