DEV Community

Cover image for Querying Spain's Registro Mercantil: how to parse BORME data via MCP
OpenRegistry
OpenRegistry

Posted on

Querying Spain's Registro Mercantil: how to parse BORME data via MCP

#compliance #mcp #fintech #programming

Spain's corporate registry network distributes company filings across local provincial databases. The central Registro Mercantil Central in Madrid acts as an oversight body, but the records reside locally. Every registered Spanish company carries a unique nine-character Número de Identificación Fiscal (NIF). The leading character of this tax number indicates the corporate form. A "B" denotes a limited liability company (Sociedad de Responsabilidad Limitada). An "A" signals a public limited company (Sociedad Anónima). By law, any corporate filing or change only becomes opposable to third parties once published in the Boletín Oficial del Registro Mercantil (BORME).

For analysts and compliance officers conducting M&A diligence, querying these provincial databases directly is the only way to guarantee data integrity. Relying on cached data from the legacy paid databases risks missing recent management changes or insolvency filings. The OpenRegistry Model Context Protocol (MCP) server connects directly to these official sources. This connection enables AI assistants and programmatic workflows to query live Spanish registry records.

Raw registry payload structure

When you query a Spanish entity, the registry returns provincial filings alongside basic company identifiers. The OpenRegistry MCP server delivers this raw payload inside the jurisdiction_data object. It leaves the schema intact.

The JSON payload contains several key fields:

  • nif: The registered tax identification number.
  • denominacion: The official registered name of the corporation.
  • provincia: The provincial registry office holding the company’s books.
  • estado: The legal status of the company.
  • actos_inscritos: The chronological ledger of gazetted acts published in the BORME.

The actos_inscritos array provides crucial compliance data. Each item includes a publication date, a section code, and a description of the corporate action. These events include capital modifications, director appointments, or dissolution proceedings. Capital markets teams use this array to build a verified timeline of corporate changes directly from the primary source.

The CJEU ruling and beneficial ownership

Following the Court of Justice of the European Union (CJEU) ruling in joined cases C-37/20 and C-601/20, access to ultimate beneficial ownership (UBO) databases changed across Europe. Spain codifies these restrictions strictly. Access to the Registro de Titularidades Reales is legally gated. Only entities demonstrating a statutory legitimate interest can query it. This includes financial institutions, notary publics, and law enforcement executing anti-money laundering (AML) tasks.

Because of these rules, no public API can return automated Spanish UBO data. OpenRegistry operates within these regulatory boundaries. The tools return public officers, administrators, and historical gazette filings. They do not bypass statutory AML gates. If a data vendor claims to offer instant, ungated Spanish UBO data, they are serving stale, scraped databases. Or they are using probabilistic estimates instead of live registry records.

Querying the registry via MCP

To find a Spanish entity, invoke the search_companies tool with the ES jurisdiction code. Searching by NIF provides the most direct match. Name queries are also supported.

{
  "name": "search_companies",
  "arguments": {
    "query": "B88123456",
    "jurisdiction": "ES"
  }
}
Enter fullscreen mode Exit fullscreen mode

Once you have the registration identifier from the search results, query the profile details using the get_company_profile tool to retrieve the current state of the company.

{
  "name": "get_company_profile",
  "arguments": {
    "company_id": "ES-B88123456",
    "jurisdiction": "ES"
  }
}
Enter fullscreen mode Exit fullscreen mode

This request connects directly to the provincial registry system to fetch the company's standing, registered address, and gazetted BORME filings. The integration bypasses middle-tier databases, keeping your compliance trail clean and verifiable.

Verification workflows for finance teams

For analysts checking acquisition targets or compliance officers assessing counterparties, live data prevents transaction errors. When a Spanish counterparty changes its sole administrator or reduces its share capital, global corporate aggregators often take weeks to reflect the update.

Integrating the BORME gazette timeline into your analytical platform lets your team verify active signers before executing agreements. This approach mitigates risk and aligns with European diligence standards. To query the Spanish registry alongside 26 other national jurisdictions without API key barriers, point your client to openregistry.sophymarine.com and start the server.

Top comments (0)