Remote MCP · Endpoint

Japan Restaurant Calories MCP server

No. Japan Restaurant Calories answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://calories.omikuji.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.omikuji/calories
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
477 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Nutrition facts for 24,000+ menu items of 100+ Japanese restaurant chains, with sources.
Listing
From the official MCP registry (active).
Recent checks of Japan Restaurant Calories
CheckedResultHandshake
43 minutes agoHandshake completed477 ms
8 days agoHandshake completed407 ms
9 days agoHandshake completed436 ms
11 days agoHandshake completed557 ms
12 days agoHandshake completed534 ms
13 days agoHandshake completed391 ms
14 days agoHandshake completed77 ms
14 days agoHandshake completed449 ms
16 days agoHandshake completed363 ms
19 days agoHandshake completed335 ms
21 days agoHandshake completed398 ms
24 days agoHandshake completed274 ms
26 days agoHandshake completed198 ms
28 days agoHandshake completed315 ms

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

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 Japan Restaurant Calories and makes no claim about it beyond what these checks measured.