Remote MCP · Endpoint

Oku-Akasaka Sushi Tanji MCP server

No. Oku-Akasaka Sushi Tanji answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://sushi-tanji.com/wp-json/bmp/v1/mcp

The last check completed an MCP handshake.

Registry name
com.sushi-tanji/reservations
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
876 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Omakase courses at a sushi counter in Akasaka, Tokyo, with a pre-filled link to the booking page.
Listing
From the official MCP registry (active).
Recent checks of Oku-Akasaka Sushi Tanji
CheckedResultHandshake
57 minutes agoHandshake completed876 ms
3 days agoHandshake completed572 ms
12 days agoHandshake completed591 ms
13 days agoHandshake completed770 ms
15 days agoHandshake completed784 ms
15 days agoHandshake completed825 ms
17 days agoHandshake completed818 ms
18 days agoHandshake completed571 ms
18 days agoHandshake completed552 ms
20 days agoHandshake completed553 ms
22 days agoHandshake completed748 ms
25 days agoHandshake completed680 ms
27 days agoHandshake completed793 ms
29 days agoHandshake completed747 ms

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

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 Oku-Akasaka Sushi Tanji and makes no claim about it beyond what these checks measured.