Remote MCP · Endpoint
エキテン ネット予約 MCP server
No. エキテン ネット予約 answered an MCP handshake 4 hours ago.
UpLast checked 4 hours ago
Server URL
https://eapi.ekiten.jp/mcp/reservation
The last check completed an MCP handshake.
- Registry name
- jp.ekiten.eapi/ekiten-reservation
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-11-25
- Handshake latency
- 718 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- エキテン（日本全国のお店・施設の情報サイト）のネット予約を提供するMCPサーバー。オールジャンルの日本国内店舗・施設が対象。店舗検索・空き確認・予約登録・キャンセルに対応。
- Website
- https://eapi.ekiten.jp/mcp/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 4 hours ago | Handshake completed | 718 ms |
| 15 hours ago | Handshake completed | 689 ms |
| 1 day ago | Handshake completed | 713 ms |
| 2 days ago | Handshake completed | 697 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 エキテン ネット予約 and makes no claim about it beyond what these checks measured.