Remote MCP · Endpoint

AV女優判定AI MCP server

No. AV女優判定AI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
884 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
日本の成人向け作品 (18歳以上) の出演者・作品検索。画像からの出演者判定はサイトで発行する認証コードが必要。
Listing
From the official MCP registry (active).
Recent checks of AV女優判定AI
CheckedResultHandshake
1 hour agoHandshake completed884 ms
1 day agoHandshake completed1.34 s
2 days agoHandshake completed842 ms
3 days agoHandshake completed821 ms
4 days agoHandshake completed811 ms
5 days agoHandshake completed878 ms
6 days agoHandshake completed864 ms
9 days agoHandshake completed799 ms
11 days agoHandshake completed852 ms
14 days agoHandshake completed218 ms
16 days agoHandshake completed871 ms
18 days agoHandshake completed929 ms
20 days agoHandshake completed1.04 s
22 days agoHandshake completed738 ms
24 days agoHandshake completed952 ms
26 days agoHandshake completed948 ms
27 days agoHandshake completed811 ms
29 days agoHandshake completed1.25 s

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 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 AV女優判定AI and makes no claim about it beyond what these checks measured.