Remote MCP · Endpoint
Systemia Website Audit MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://base44.app/api/apps/698cb6dd30475e7649f4fdcd/functions/auditAgentMcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.jgaethle10/systemia-website-audit
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 36.8% from 19 checks
- Described by its publisher as
- Website, local SEO, performance and conversion audits with human-confirmed checkout.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 1 day ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 3 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 5 days ago | Failed - the server returned an HTTP error | — |
| 6 days ago | Failed - the server returned an HTTP error | — |
| 8 days ago | Failed - the server returned an HTTP error | — |
| 11 days ago | Failed - the server returned an HTTP error | — |
| 13 days ago | Failed - the server returned an HTTP error | — |
| 15 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Handshake completed | 243 ms |
| 22 days ago | Handshake completed | 237 ms |
| 24 days ago | Handshake completed | 397 ms |
| 26 days ago | Handshake completed | 205 ms |
| 27 days ago | Handshake completed | 350 ms |
| 29 days ago | Handshake completed | 462 ms |
| 29 days ago | Handshake completed | 569 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 28.
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 Systemia Website Audit and makes no claim about it beyond what these checks measured.