# Japan Restaurant Calories (remote · calories.omikuji.dev)

Nutrition facts for 24,000+ menu items of 100+ Japanese restaurant chains, with sources.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `calories.omikuji.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/dev-omikuji-calories/calories.md), [page](https://verifymcp.io/servers/dev-omikuji-calories/calories)

## Channel facts

- Endpoint: `https://calories.omikuji.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-omikuji-calories 'https://calories.omikuji.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-omikuji-calories": {
      "url": "https://calories.omikuji.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-omikuji-calories": {
      "type": "http",
      "url": "https://calories.omikuji.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-omikuji-calories]
url = "https://calories.omikuji.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-omikuji-calories": {
      "type": "remote",
      "url": "https://calories.omikuji.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-omikuji-calories --url 'https://calories.omikuji.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-omikuji-calories:
    url: "https://calories.omikuji.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-omikuji-calories": {
      "Transport": "http",
      "Url": "https://calories.omikuji.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-omikuji-calories -t streamable-http -u 'https://calories.omikuji.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-omikuji-calories": {
      "type": "http",
      "url": "https://calories.omikuji.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 73, 0)

- [security] 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
- [functional regression] Schema quality: 170 → 263
- [functional improvement] Tool coverage: 43% → 50%
- [functional] Server version: 2026-10-22 → 2026-10-23
- [cosmetic] “request_missing” reworded the description of “chain”
- [cosmetic] “search_menu” reworded the description of “nutrient”
- [cosmetic] “search_menu” reworded the description of “sort”

### 2026-10-22 (score 73, +1)

- [functional] Server version: 2026-10-20 → 2026-10-22

### 2026-10-21 (score 72, 0)

- [functional] Server version: 2026-10-19 → 2026-10-20

### 2026-10-20 (score 72, +1)

- [functional] Server version: 2026-10-18 → 2026-10-19

### 2026-10-18 (score 71, 0)

- [functional] Server version: 2026-10-12 → 2026-10-18

### 2026-10-17 (score 71, +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.

### 2026-10-16 (score 70, 0)

- [security] 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
- [functional improvement] Stability: unverified → 0.03

### 2026-10-15 (score 70)

First indexed and scored.

## MCP tools (4)

### `search_menu` (~644 tokens)

Search menu items

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.

Input parameters:

- `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.

### `sum_items` (~56 tokens)

Total a meal

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.

Input parameters:

- `items` (array, required)

### `list_chains` (~57 tokens)

List covered chains

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.

Input parameters:

- `query` (string)

### `request_missing` (~160 tokens)

Request a missing chain or item

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.

Input parameters:

- `chain` (string, required): 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".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-omikuji-calories/calories#diagnostics

## Score history

- 2026-10-23: 73
- 2026-10-22: 73
- 2026-10-21: 72
- 2026-10-20: 72
- 2026-10-19: 71
- 2026-10-18: 71
- 2026-10-17: 71
- 2026-10-16: 70
- 2026-10-15: 70

## Common questions

### 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.

## Links

- Remote endpoint: https://calories.omikuji.dev/mcp
- Website: https://calories.omikuji.dev/ai/
- Changelog RSS feed: https://verifymcp.io/servers/dev-omikuji-calories/calories.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-omikuji-calories/calories.json
- HTML version of this page: https://verifymcp.io/servers/dev-omikuji-calories/calories