Japan Restaurant Calories MCP server
dev.omikuji/caloriesomikuji.devstreamable-httpv1.0.0Scanned
Nutrition facts for 24,000+ menu items of 100+ Japanese restaurant chains, with sources.
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Japan Restaurant Calories MCP server can do
The Japan Restaurant Calories MCP server is published by omikuji.dev, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: sum_items and request_missing), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
request_missingTell the site operator that a restaurant chain or menu item is missing.No findings
Why it is in this group
- The name "request_missing" says "request": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- title: Request a missing chain or item
sum_itemsAdd up nutrition for a set of items (a meal, a day) using ids from search_menu.1 finding
Why it is in this group
- The description's first verb is "add": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "sum_items" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "add": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Total a meal
Only reads 2Show 2 read-only tools
list_chainsList the restaurant chains, stores and packaged-food makers covered (makers have type: packaged_food_maker), with item counts (current items only), which nutrients each chain publi…No findings
Why it is in this group
- The name "list_chains" says "list": a word for reading.
Description, as the server wrote it List the restaurant chains, stores and packaged-food makers covered (makers have type: packaged_food_maker), 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: List covered chains
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://calories.omikuji.dev/mcp: tools/list returned 4 tools to an anonymous client, including sum_items (write), request_missing (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnsum_items
The server marks "sum_items" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "add": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:list_chainsOnly readsdescription
- Changed:request_missingChanges thingsinputSchema
- Changed:search_menuOnly readsdescriptioninputSchema
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http calories https://calories.omikuji.dev/mcpclaude mcp add --transport http calories https://calories.omikuji.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__calories__search_menu",
"mcp__calories__list_chains"
],
"ask": [
"mcp__calories__sum_items",
"mcp__calories__request_missing"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as calories. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.omikuji/calories/verify?hash=b712f70b72d0def6a4a4f6e124f955fb9941a4ec458c5611bdc0f6609a81bcd0" | jq -e '.changed == false'Pinned hash b712f70b72d0, from Nov 15, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.omikuji/calories/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.omikuji/calories)Source: MCP Registry. Synced Oct 21, 2026, 18:11 UTC.
Japan Restaurant Calories MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Japan Restaurant Calories MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Japan Restaurant Calories MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Japan Restaurant Calories MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Japan Restaurant Calories MCP server have?
- 4 tools: 2 write, 2 read. sum_items, request_missing, search_menu and list_chains.
Does the Japan Restaurant Calories MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Japan Restaurant Calories MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Japan Restaurant Calories MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.