Remote MCP · Endpoint
AV女優判定AI MCP server
No. AV女優判定AI answered an MCP handshake 46 minutes ago.
UpLast checked 46 minutes ago
Server URL
https://ai-for-av.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.ai-for-av/ai-for-av
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 872 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- 日本の成人向け作品 (18歳以上) の出演者・作品検索。画像からの出演者判定はサイトで発行する認証コードが必要。
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 46 minutes ago | Handshake completed | 872 ms |
| 3 hours ago | Handshake completed | 842 ms |
| 1 day ago | Handshake completed | 856 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 AV女優判定AI and makes no claim about it beyond what these checks measured.