Entityindex MCP server

• Registry nameai.entityindex/entityindexverified in the MCP registry

The registry name sits under entityindex.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-28
• Tools6
• Server calls itselfentityindex
• Server version1.1.0
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 87 ms.

• Its tools do every use case we checked: query a verified business index through an API or MCP server; find ski-in ski-out hotels in Grandvalira, Andorra.
• Checked on 5 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring5 of the 7 daily checks it takes to print a share
• Median first answer154 ms
• Space in an agent's context≈ 1,420 tokensthe definitions of all its tools (6), which an agent carries on every turn
• Tool definitionsA · 92 of 100
• Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 3 of 6

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_hotels

  Use this when a user asks for accommodation in Andorra, e.g. 'ski-in/ski-out hotel in Grandvalira', 'hotel with spa in Andorra', 'pet-friendly hotel in Canillo', 'family hotel in Soldeu or El Tarter', 'hotel with parking in Pas de la…

• get_hotel

  Use after search_hotels when the user wants details or a booking link for one property. Input: slug from search_hotels (e.g. 'hotel-nordic'). Returns every verified fact with its source URL and check date, notes from the official site…

• list_areas

  Use to discover which parishes and localities have accommodation in the index (with counts) before filtering search_hotels by area, or to answer 'where can I stay in Andorra?'.

• search_entities

  Generic search across entityindex.ai verticals; same data as the vertical-specific tools. Today the only vertical is 'hotels' (country 'andorra'); call list_verticals to see what exists. Parameters: vertical (required), country, area…

• get_entity

  Generic record lookup: vertical + slug (from search_entities). Same output as the vertical-specific get tool (e.g. get_hotel). Example: {"vertical":"hotels","slug":"hotel-nordic"}.

• list_verticals

  Lists the verticals (business types), countries and response languages (en, es, fr, ca) available in entityindex.ai, with their filters, URL pattern /{country}/{vertical}/{slug}/ and record counts. Today: hotels in Andorra.