_ registry / mcp streamable-http · checked 1h ago

calories-omikuji-dev

https://calories.omikuji.dev

Registry code: 837e6a579271508e

api record

Nutrition facts (kcal, protein, fat, carbs, salt, and for some chains vitamins/minerals) for menu items of major Japanese restaurant chains, collected from each chain's published nutrition tables. Search in Japanese (item names are Japanese, e.g. 牛丼 並盛, チーズバーガー, 唐揚げ). Use list_chains to see which chains are covered, search_menu to find items, and sum_items to total a meal. If something the user wants is really not covered, request_missing tells the operator. When answering, cite the item url or the chain's source_file. Do not use this data for allergy decisions.

endpoint
https://calories.omikuji.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is calories-omikuji-dev live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is calories-omikuji-dev free to use?
Yes — the hub reached it with no key and no payment.
What tools does calories-omikuji-dev have?
4 tools: request_missing, search_menu, sum_items, list_chains.
Is calories-omikuji-dev safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
473ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_chains open 1h ago

    List the restaurant chains covered, with item counts, which nutrients each chain publishes, the source document and when it was fetched. query filters by chain name.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 9 lines
  • request_missing unknown never probed

    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. Send one request per chain or item; do not send the user's personal information. 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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "chain"
  ],
  "properties": {
    "item": {
      "type": "string",
      "maxLength": 100,
      "description": "Menu item name, if a specific item is missing."
    },
    "note": {
      "type": "string",
      "maxLength": 300,
      "description": "Optional short context, e.g. \"seasonal item\", \"new menu from October\"."
    },
    "chain": {
      "type": "string",
      "maxLength": 60,
      "description": "Restaurant chain name, e.g. 丸亀製麺."
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • search_menu unknown 1h ago

    Search menu items of Japanese restaurant chains and get their nutrition facts. 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). With a query, results are sorted by how well the item name matches (default sort "relevance"); otherwise by kcal ascending. Each item has an id for sum_items, a page url, and the chain's source_file.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "sort": {
      "enum": [
        "relevance",
        "kcal_asc",
        "kcal_desc",
        "nutrient_asc",
        "nutrient_desc"
      ],
      "type": "string"
    },
    "chain": {
      "type": "string",
      "description": "Chain id from list_chains, or its Japanese name / nickname."
    },
    "genre": {
      "enum": [
        "デザート",
        "ドリンク",
        "ごはん・サイド",
        "寿司",
        "麺類",
        "カレー",
        "丼もの",
        "バーガー",
        "ピザ",
        "揚げ物",
        "ステーキ・肉料理",
        "餃子・中華",
        "定食・セット",
        "サラダ・野菜",
        "スープ・汁物",
        "調味料・トッピング",
        "その他"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Words to match, e.g. \"牛丼 並盛\", \"チーズバーガー\", \"すき家 カレー\"."
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "maximum": 1000,
      "minimum": 0
    },
    "max_kcal": {
      "type": "number"
    },
    "min_kcal": {
      "type": "number"
    },
    "nutrient": {
      "enum": [
        "kcal",
        "protein_g",
        "fat_g",
        "saturated_g",
        "carb_g",
        "sugar_g",
        "fiber_g",
        "salt_g",
        "sodium_mg",
        "potassium_mg",
        "calcium_mg",
        "phosphorus_mg",
        "iron_mg",
        "vit_a_ug",
        "retinol_ug",
        "carotene_ug",
        "vit_b1_mg",
        "vit_b2_mg",
        "niacin_mg",
        "vit_c_mg",
        "vit_d_ug",
        "vit_e_mg",
        "cholesterol_mg",
        "ash_g",
        "weight_g"
      ],
      "type": "string",
      "description": "Only items that publish this nutrient."
    }
  },
  "additionalProperties": false
}
    arguments 95 lines
  • sum_items unknown 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "items"
  ],
  "properties": {
    "items": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id"
        ],
        "properties": {
          "id": {
            "type": "string",
            "description": "id from search_menu, e.g. \"sukiya/牛丼-並盛\"."
          },
          "quantity": {
            "type": "number",
            "default": 1,
            "maximum": 20,
            "minimum": 0.1
          }
        },
        "additionalProperties": false
      },
      "maxItems": 30
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 837e6a579271508e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/837e6a579271508e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/837e6a579271508e/badge.svg)](https://brick.blue/agent/837e6a579271508e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on omikuji.dev 3 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.