Skip to content
LicitaIA logo

LicitaIA MCP server

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

read 2026-10-20

← Back to LicitaIA

Whose server it is
  • Registry nameorg.licitaia/licitacionesverified in the MCP registry

The registry name sits under licitaia.org. 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-20
  • Stateanswerschecked 2026-10-20
  • Tools2
  • Server calls itselflicitaia-public
  • Server version1.0.0
  • Protocol version2025-06-18

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

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: Set alerts by CPV code and province; Analyse tender specifications for requirements and deadlines.

Once connected

  • Parameters are untyped or undescribed in 2 of 2 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: 16, the first on 2026-10-20
  • INITE MCP score68 of 100answers 100 · does the job 0 · definitions 83 · context 100 · connects 100
  • What an agent can do with it0 of 2 use cases
  • Answered100% of days16 of 16 daily checks
  • Median first answer527 ms
  • Space in an agent's context≈ 431 tokensthe definitions of all its tools (2), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 2

What an agent can do with it

  • not sure · Search public tenders on PLACSP and TED
  • cannot · Set alerts by CPV code and province
  • cannot · Analyse tender specifications for requirements and deadlines

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

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 (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 →

Tools it offers2 tools · read 2026-10-20
  • buscar_licitaciones

    Búsqueda pública acotada a publicaciones de los últimos 30 días. Opcionalmente usa soloFuturas para exigir un plazo posterior al momento de consulta, fechaLimiteDesde como límite inclusivo ISO 8601 con zona horaria, y…

  • ficha_licitacion

    Ficha pública por UUID, sin documentos, IA, perfil ni veredictos.

How to connect

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

{
  "mcpServers": {
    "licitaciones": {
      "type": "http",
      "url": "https://api.licitaia.org/api/mcp/public"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http licitaia https://api.licitaia.org/api/mcp/public

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.licitaia.org/api/mcp/public 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.