Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

The Omelette Index

REMOTE · API.OMELETTEINDEX.COM · SCANNED OCT 2

Purchasing power via plain-omelette prices: country, region and city readings in EUR, worldwide.

+1 this week 81 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 385 tokens (~77/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
Install

How do I install the The Omelette Index MCP server?

The Omelette Index is a hosted endpoint at https://api.omeletteindex.com/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 · api.omeletteindex.com

# add to Claude Code
claude mcp add --transport http com-omeletteindex-omelette-index 'https://api.omeletteindex.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-omeletteindex-omelette-index": {
      "url": "https://api.omeletteindex.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-omeletteindex-omelette-index": {
      "type": "http",
      "url": "https://api.omeletteindex.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-omeletteindex-omelette-index]
url = "https://api.omeletteindex.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-omeletteindex-omelette-index": {
      "type": "remote",
      "url": "https://api.omeletteindex.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-omeletteindex-omelette-index --url 'https://api.omeletteindex.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-omeletteindex-omelette-index:
    url: "https://api.omeletteindex.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-omeletteindex-omelette-index": {
      "Transport": "http",
      "Url": "https://api.omeletteindex.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-omeletteindex-omelette-index -t streamable-http -u 'https://api.omeletteindex.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-omeletteindex-omelette-index": {
      "type": "http",
      "url": "https://api.omeletteindex.com/mcp"
    }
  }
}

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

Changelog

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 2 Oct 2026 · Probed https://api.omeletteindex.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.omeletteindex.com CN=YE2,O=Let's Encrypt,C=US 8 Sept 2026 7 Dec 2026 ECDSA 256 ECDSA-SHA384 6cca18356c442a34b431487d11ecd9d779e
SANs: api.omeletteindex.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.omeletteindex.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
omeletteindex.com. 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; preload
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://api.omeletteindex.com/mcp Verified 200
http (plaintext) http://api.omeletteindex.com/mcp HTTPS enforced 308 https://api.omeletteindex.com/mcp
MCP tools · 5 exposed · ~277 tokens

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 →

Tool Tokens
cities ~64

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

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 country code
querystring–Case-insensitive substring of the city name

No output schema declared.

No examples provided.

compare ~44

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

NameTypeReqDescription
countriesarrayyesISO 3166-1 alpha-2 country codes

No output schema declared.

No examples provided.

country_index ~67

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.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 country code, e.g. US, DE, SE

No output schema declared.

No examples provided.

index_overview ~51

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

subdivisions ~51

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

NameTypeReqDescription
countrystringyesISO 3166-1 alpha-2 country code

No output schema declared.

No examples provided.

Common questions

What is the The Omelette Index MCP server?

The Omelette Index is an MCP server listed in the public MCP registry as com.omeletteindex/omelette-index. Purchasing power via plain-omelette prices: country, region and city readings in EUR, worldwide. This page covers its hosted endpoint (https://api.omeletteindex.com/mcp).

Is the The Omelette Index MCP server safe to use?

The Omelette Index scores 81 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 The Omelette Index MCP server expose?

The Omelette Index exposes 5 tools: index_overview, country_index, subdivisions, cities, compare. Their descriptions and schemas cost roughly 277 tokens of context every time the server is loaded.

Does the The Omelette Index MCP server require authentication?

No. We connected to The Omelette Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the The Omelette Index MCP server still maintained?

The Omelette Index is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.