Remote MCP · Endpoint
Webhook Admin MCP server
No — it is up, but it requires credentials. Webhook Admin answered 4 days ago with an authentication challenge rather than a session.
Auth requiredLast checked 4 days ago
Server URL
https://api.webhookadmin.com/mcp
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- com.webhookadmin/webhookadmin
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 16 checks
- Described by its publisher as
- Webhook の送信・再送・監視を行う Webhook 統合インテグレーション (日本製)。送信先・イベントの種類・API キーを tool で扱う。管理画面のアカウントでログイン (OAuth)
- Website
- https://webhookadmin.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 4 days ago | Credentials required | — |
| 4 days ago | Credentials required | — |
| 5 days ago | Credentials required | — |
| 7 days ago | Credentials required | — |
| 8 days ago | Credentials required | — |
| 9 days ago | Credentials required | — |
| 10 days ago | Credentials required | — |
| 11 days ago | Credentials required | — |
| 12 days ago | Credentials required | — |
| 15 days ago | Credentials required | — |
| 18 days ago | Credentials required | — |
| 20 days ago | Credentials required | — |
| 22 days ago | Credentials required | — |
| 24 days ago | Credentials required | — |
| 26 days ago | Credentials required | — |
| 28 days ago | Credentials required | — |
| 30 days ago | Credentials required | — |
| 32 days ago | Credentials required | — |
| 33 days ago | Credentials required | — |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 26 responding of 26.
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 Webhook Admin and makes no claim about it beyond what these checks measured.