Japan Restaurant Calories
REMOTE · CALORIES.OMIKUJI.DEV
Nutrition facts for 24,000+ menu items of 100+ Japanese restaurant chains, with sources.
Available components
Last scanned (21 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1053 tokens (~263/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 0
- Tool “list_chains” rewrote its description, which is the text the model reads security
- Tool “search_menu” rewrote its description, which is the text the model reads security
- Schema quality: 170 → 263 ▼ functional
- Tool coverage: 43% → 50% ▲ functional
- Server version: 2026-10-22 → 2026-10-23 functional
- “request_missing” reworded the description of “chain” cosmetic
- “search_menu” reworded the description of “nutrient” cosmetic
- “search_menu” reworded the description of “sort” cosmetic
- 22 Oct 26 +1
- Server version: 2026-10-20 → 2026-10-22 functional
- 21 Oct 26 0
- Server version: 2026-10-19 → 2026-10-20 functional
- 20 Oct 26 +1
- Server version: 2026-10-18 → 2026-10-19 functional
- 18 Oct 26 0
- Server version: 2026-10-12 → 2026-10-18 functional
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “request_missing” rewrote its description, which is the text the model reads security
- Tool “search_menu” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://calories.omikuji.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=omikuji.dev | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 14f2de63cee5ac82137eb86a39849ed1 |
| SANs: omikuji.dev, *.omikuji.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of calories.omikuji.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| omikuji.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://calories.omikuji.dev/mcp | Verified | 200 | |
| http (plaintext) | http://calories.omikuji.dev/mcp | HTTPS enforced | 301 | https://calories.omikuji.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_chains List covered chains ~57
List the restaurant chains covered, with item counts (current items only), which nutrients each chain publishes and when the data was fetched. query filters by chain name and also returns each chain's source document URL.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
No output schema declared.
No examples provided.
request_missing Request a missing chain or item ~160
Tell the site operator that a restaurant chain or menu item is missing. Use only after search_menu / list_chains could not find it AND the user actually wanted it. One request per chain or item. Only the chain, item and note are stored (no personal information is needed or kept). Requests are counted (not shown publicly) and used to decide what to add next. Some chains do not publish nutrition values at all, so a request does not guarantee coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Restaurant chain name, e.g. 天下一品. |
| item | string | – | Menu item name, if a specific item is missing. |
| note | string | – | Optional short context, e.g. "seasonal item", "new menu from October". |
No output schema declared.
No examples provided.
search_menu Search menu items ~644
Search menu items of Japanese restaurant chains and get their nutrition facts. Queries that return no results are counted anonymously (the query text and chain only) to decide which chains to add. query matches item name, size, category, genre and chain name (Japanese; spaces mean AND; katakana/hiragana and full/half width are treated alike; common chain nicknames like ケンタ, マック, サイゼ work). Combine with chain / genre / kcal range. Use nutrient to find items rich in a nutrient (only chains that publish it). Default order: with nutrient, by that nutrient descending; else with a query, by how well the item name matches ("relevance"); otherwise by kcal ascending. total includes discontinued items (listed last), so it can be larger than item_count in list_chains. Each item has an id for sum_items, a page url, and the chain's source_file.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain id from list_chains, or its Japanese name / nickname. |
| genre | string | – | – |
| limit | integer | – | – |
| max_kcal | number | – | – |
| min_kcal | number | – | – |
| nutrient | string | – | Only items that publish this nutrient. net_carb_g is net carbohydrate (carbohydrate minus fiber, 糖質); sugar_g is sugars (糖類) — different quantities. Keys: kcal=エネルギー(kcal), protein_g=たんぱく質(g), fat_g=… |
| offset | integer | – | – |
| query | string | – | Words to match, e.g. "牛丼 並盛", "チーズバーガー", "すき家 カレー". |
| sort | string | – | Default: nutrient_desc when nutrient is given, else relevance when query is given, else kcal_asc. |
No output schema declared.
No examples provided.
sum_items Total a meal ~56
Add up nutrition for a set of items (a meal, a day) using ids from search_menu. Nutrients that some items do not publish are reported in incomplete, because their total is an underestimate.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
How do I install the Japan Restaurant Calories MCP server?
Japan Restaurant Calories is a hosted endpoint at https://calories.omikuji.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · calories.omikuji.dev
claude mcp add --transport http dev-omikuji-calories 'https://calories.omikuji.dev/mcp'
What is the Japan Restaurant Calories MCP server?
Japan Restaurant Calories is an MCP server listed in the public MCP registry as dev.omikuji/calories. Nutrition facts for 24,000+ menu items of 100+ Japanese restaurant chains, with sources. This page covers its hosted endpoint (https://calories.omikuji.dev/mcp).
Is the Japan Restaurant Calories MCP server safe to use?
Japan Restaurant Calories scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Japan Restaurant Calories MCP server expose?
Japan Restaurant Calories exposes 4 tools: search_menu, sum_items, list_chains, request_missing. Their descriptions and schemas cost roughly 917 tokens of context every time the server is loaded.
Does the Japan Restaurant Calories MCP server require authentication?
No. We connected to Japan Restaurant Calories without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Japan Restaurant Calories MCP server still maintained?
Japan Restaurant Calories is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.