_ registry / mcp http-sse · checked 3h ago

omeletteindex

https://api.omeletteindex.com

Registry code: 047f83577c7127f0

api record

The Omelette Index: purchasing-power data based on the price of a plain omelette (three eggs and butter) at restaurants, cafes and hotels worldwide, compiled by Intuitive Bricks AB and Strömvägen 10 Invest AB. Prices are in EUR unless noted; each price splits into ingredients and service (labour, rent, margin). Figures use trimmed medians over readings from the last 90 days; a scope publishes at 8+ readings. Link to https://omeletteindex.com when presenting results.

endpoint
https://api.omeletteindex.com/mcp
protocol
http-sse ·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 omeletteindex live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is omeletteindex free to use?
Not measured yet.
What tools does omeletteindex have?
5 tools: compare, index_overview, cities, country_index, subdivisions.
Is omeletteindex 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
99.6%

90 days 99.4%· all time 99.4%

latency
330ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 362 checks · signed record
  • degraded → live
  • live → degraded· fetch failed
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • get omelette price index by country
  • compare purchasing power across countries
  • get omelette prices by city
takes → gives
text → data
tools
5 reads
_ 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 5 tools
5 never probed 0 of 5 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.

  • compare reads unknown never probed

    Side-by-side omelette index readings for two or more countries, ranked by price in EUR.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "countries"
      ],
      "properties": {
        "countries": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 2,
            "minLength": 2
          },
          "maxItems": 20,
          "minItems": 2,
          "description": "ISO 3166-1 alpha-2 country codes"
        }
      }
    }
    arguments 20 lines
  • index_overview reads unknown never probed

    Descriptive statistics for The Omelette Index: how many places serve a plain omelette, countries/subdivisions/cities published, the global price centre in EUR, and the dearest and cheapest published countries.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • cities reads unknown never probed

    Published city readings ranked by price (EUR). Optionally filter by country code or by a substring of the city name.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "query": {
          "type": "string",
          "description": "Case-insensitive substring of the city name"
        },
        "country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "ISO 3166-1 alpha-2 country code"
        }
      }
    }
    arguments 16 lines
  • country_index reads unknown never probed

    The omelette price index by country. Without arguments: every published country ranked by price (EUR, trimmed median). With a country: that country's full reading.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "ISO 3166-1 alpha-2 country code, e.g. US, DE, SE"
        }
      }
    }
    arguments 12 lines
  • subdivisions reads unknown never probed

    Published state/province readings inside one country, ranked by price, with each subdivision measured against its own country (vsCountryPct).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "country"
      ],
      "properties": {
        "country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "ISO 3166-1 alpha-2 country code"
        }
      }
    }
    arguments 15 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 047f83577c7127f0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/047f83577c7127f0/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/047f83577c7127f0/badge.svg)](https://brick.blue/agent/047f83577c7127f0?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
90%

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.