Skip to content
Azul CR logo

Azul CR MCP server

Which servers in the official MCP registry are Azul CR's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-21

← Back to Azul CR

Whose server it is
  • Registry namecr.azul/azul-crverified in the MCP registry

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

When we asked itchecked 2026-10-21
  • Stateanswerschecked 2026-10-21
  • Tools6
  • Server calls itselfazul-cr
  • Server version2.1.0
  • Protocol version2025-06-18

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

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 4 of 6 tools: check arguments before calling.

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.

Measured dailydaily checks: 1, the first on 2026-10-21
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer355 ms
  • Space in an agent's context≈ 690 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsC · 72 of 100
  • Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 4 of 6
  • Not saying whether it only reads or can destroy: 6 of 6

Worth a look

None of the five warning signs in these definitions.

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 (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). 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 →

Tools it offers6 tools · read 2026-10-21
  • search_businesses

    Search for businesses in Costa Rica by keyword, city, or industry. Returns business name, city, industry, hours, tier, and a citation-ready URL on azul.cr. Contact details (WhatsApp/phone) require a keyed connection.

  • get_business

    Get public details of a specific business by its slug. Returns name, about, hours, tier, rating, and citation URL. WhatsApp/phone/address require a keyed connection.

  • find_jobs

    Search for job postings in Costa Rica. Returns title, employer, type (full/part/contract), salary, city, and URL. WhatsApp apply link requires a keyed connection.

  • get_events

    List upcoming events in Costa Rica. Returns title, date, venue, city, organizer, and URL.

  • get_specials

    List active deals and offers in Costa Rica. Returns title, discount, business, city, expiry, and URL. WhatsApp requires a keyed connection.

  • semantic_search

    AI-powered semantic search across all Azul CR content (businesses, jobs, events, specials). Understands natural language queries like "kid-friendly outdoor activity near the beach" or "dentista que hable inglés en Liberia". Uses bge-m3…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "azul-cr": {
      "type": "http",
      "url": "https://azul.cr/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http azul https://azul.cr/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://azul.cr/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.