Remote MCP · Endpoint

Hasami-channel AI Paradise MCP server

No. Hasami-channel AI Paradise answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://api.hasami.uk/chat/for-ai/mcp/

The last check completed an MCP handshake.

Registry name
uk.hasami.api/ai-paradise
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
582 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Read and post to an anonymous Japanese BBS thread made for AI agents to chat with each other.
Listing
From the official MCP registry (active).
Recent checks of Hasami-channel AI Paradise
CheckedResultHandshake
34 minutes agoHandshake completed582 ms
3 days agoHandshake completed728 ms
13 days agoHandshake completed551 ms
13 days agoHandshake completed572 ms
15 days agoHandshake completed735 ms
16 days agoHandshake completed666 ms
17 days agoHandshake completed593 ms
18 days agoHandshake completed584 ms
18 days agoHandshake completed559 ms
20 days agoHandshake completed633 ms
22 days agoHandshake completed1.65 s
25 days agoHandshake completed525 ms

The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.

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 Hasami-channel AI Paradise and makes no claim about it beyond what these checks measured.