Skip to content
BORME API logo

BORME API MCP server

Which MCP servers are BORME API'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-30

← Back to BORME API

Whose server it is
  • Registry namecom.bormeapi/borme-mcpverified in the MCP registry

The registry name sits under bormeapi.com. 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-30
  • Stateanswerschecked 2026-10-30
  • Tools10
  • Server calls itselfborme
  • Server version0.1.0
  • Protocol version2025-06-18

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

Should an agent connect itNot proven either way yet
  • Its tools do Look up a company's registry sheet by tax ID, but not Monitor new gazette notices for watched companies via webhooks.
  • Checked on 4 of the 7 days it takes to judge reliability.

Once connected

  • For "Look up a company's registry sheet by tax ID", the likely first call is company_by_nif.

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: 4, the first on 2026-10-30
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • What an agent can do with it1 of 2 use cases
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer542 ms
  • Space in an agent's context≈ 4,013 tokensthe definitions of all its tools (10), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · Trace officer and director changes at Spanish companies over time
  • cannot · Monitor new gazette notices for watched companies via webhooks
  • can do · Look up a company's registry sheet by tax ID

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 offers10 tools · read 2026-10-30
  • search_events

    Search BORME registry events (since 2009) across companies by publication date, province, act type and company name, newest first. Use it for questions about many companies ("insolvency notices in Valencia in September"). For one known…

  • company_history

    Get one company's BORME timeline: its published registry events within your plan's window. Use it once the company is known (a slug from search_companies or company_by_nif); across many companies use search_events. A name instead of a…

  • company_by_nif

    Look up a Spanish company by its NIF/CIF tax ID. Use it when the user gives a tax ID (with a name use search_companies); on a hit, call company_history with the company_slug. Returns JSON {found, company_slug, company_name, current_name…

  • brand_owner

    Find the Spanish company a trademark or trading name is linked to, in the Spanish patent office's (OEPM) trademark and commercial-name records we hold (the archive starts in 1987). Use it when the user names a brand; for a company's own…

  • company_brands

    List the trademarks and trading names that the Spanish patent office (OEPM) records under a holder with this company's name. Use it for a known company (a slug from search_companies or company_history); to go from a brand to its company…

  • recent_signals

    Get a sample of the latest risk signals derived from BORME and public sources: at most 10 rows dated within the last 7 days. Use it for "what risk signals appeared this week"; not a per-company check (use company_history) and not the full…

  • daily_digest

    Summarise one BORME publication day: total events, counts by act type, the top 10 provinces and the day's insolvency-proceedings notices. Use it for "what was published today" or a day's figures; to read the notices use search_events with…

  • search_companies

    Find Spanish companies by name and return ranked company cards. Use it first when the user gives a company name, then company_history with its company_slug; with a tax ID use company_by_nif, with a brand use brand_owner. Matches current…

  • list_act_types

    List every normalized BORME act type: the enum used by the act_types filter of search_events (act_type), its Spanish label (spanish) and its English label (english). Use it to choose act_types values or to translate act types in an…

  • registry_stats

    Report the coverage and freshness of the BORME data behind this server. Use it to answer "how much data is there?", "how fresh is it?" and "can I trust date filters for period X?" before running searches; it says nothing about any one…

How to connect

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

{
  "mcpServers": {
    "borme-mcp": {
      "type": "http",
      "url": "https://mcp.bormeapi.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http bormeapi https://mcp.bormeapi.com/mcp

Add to CursorAdd to VS Code

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

OpenAPI spec

24 paths, read 2026-10-30. Open the spec ↗

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.