The Cyprus Registrar of Companies assigns every incorporated entity an HE number. That code sits at the centre of almost every lookup in DRCOR, and it passes through unchanged in the raw registry payload returned via OpenRegistry.
Finance teams encounter it constantly. Cyprus appears in many cross‑border structures, especially in holding or financing layers. A Luxembourg parent with a Cypriot treasury subsidiary is routine during acquisition screening or counterparty checks. Someone eventually asks a simple question: which legal entity filed that return? The HE number points straight to the registry entry that answers it.
OpenRegistry exposes the Cyprus register through its MCP server. An assistant can query DRCOR as the upstream source rather than relying on a secondary dataset. The response contains the registry fields exactly as published, placed inside jurisdiction_data. No translation layer sits between the assistant and the original record. The data matches what the registrar shows on its own site.
What DRCOR records actually contain
A Cyprus company profile tied to an HE number tends to be compact. The registry returns a small set of core attributes about the entity.
Typical raw fields include:
-
registration_number(the HE identifier) -
company_name -
company_status -
incorporation_date registered_office_address
Officer information arrives through a different query. Director and secretary entries include the person’s name, the role, plus the appointment date. This section often carries the useful signals during diligence. One individual appearing across several entities can expose links between companies that otherwise look unrelated.
Share capital also appears in the jurisdiction payload. Cyprus filings normally state authorised capital, issued capital and the currency attached to the shares. Those numbers matter when checking whether a financing step altered the legal capital of the company. Term sheets say many things; the register records what actually happened.
Filings are accessible as well. DRCOR publishes incorporation documents, annual returns and certain corporate updates. Each document receives its own identifier inside the registry. That number becomes the handle used to retrieve the source file.
Data the registry does not expose openly
Cyprus created a beneficial ownership register under the EU AMLD framework. Public access shifted after the CJEU ruling in case C‑601/20. Several European registers reduced open search capability soon after. Cyprus followed the same direction.
The register itself still exists. Public queries do not.
Unrestricted lookups for beneficial owners are no longer available to anonymous users. Access requires authentication and a declared legal basis. For teams building KYB workflows this sets a clear boundary around what the registry can supply automatically.
Historical state is another constraint. The registry returns the current company profile together with the filings that remain available. It does not expose a versioned snapshot of past company states. Anyone constructing a timeline has to work from the filings themselves, reading changes across documents rather than requesting a past record directly.
Querying the Cyprus registry through MCP
OpenRegistry exposes DRCOR through a small group of MCP tools. The assistant sends a tool call and receives the registry response in structured form.
Most sessions begin with a name search in the CY jurisdiction.
Example tool call:
search_companies({
"jurisdiction": "CY",
"query": "Helios Capital Holdings"
})
The response returns candidate entities together with their HE numbers. Once the number is known, the assistant can fetch the full registry profile.
get_company_profile({
"jurisdiction": "CY",
"company_number": "HE123456"
})
Officer records come next when needed.
get_officers({
"jurisdiction": "CY",
"company_number": "HE123456"
})
Filings follow the same pattern. First list them.
list_filings({
"jurisdiction": "CY",
"company_number": "HE123456"
})
Then retrieve a document by its registry identifier.
fetch_document({
"jurisdiction": "CY",
"document_id": "DRCOR-FILING-987654"
})
Each response carries two layers. The structured OpenRegistry schema appears at the top. The original registry payload sits under jurisdiction_data. Auditors sometimes insist on that second layer because it shows the exact field names returned by the source register. A reviewer can reproduce the lookup against DRCOR and confirm the values match.
Why finance teams care about the raw record
Cyprus entities appear frequently in lending structures, intellectual property holding chains and tax‑driven group arrangements. When diligence reaches one of these companies the practical question is straightforward: which legal entity actually sits at this level of the structure?
The registry profile answers it quickly. The HE number ties each filing to the company of record. Director appointments can reveal the same control group operating across several subsidiaries. Capital updates show whether funding reached the legal entity rather than remaining a paper agreement.
The legacy paid databases usually rely on periodic extracts from national registers. That works for broad screening. Timing becomes awkward when the exact filing date matters, or when a newly incorporated entity appears between refresh cycles.
A direct query to the register removes that delay. An assistant using OpenRegistry calls DRCOR and retrieves the same entry a compliance analyst would check manually. For teams building KYB pipelines or ownership graphs across jurisdictions, the verification step stays anchored to the official record.
OpenRegistry exposes the Cyprus registry through its public MCP endpoint alongside the other supported jurisdictions. Connection details and documentation sit at https://openregistry.sophymarine.com.
Top comments (0)