Irish targets often look cleaner in aggregator datasets than they do in the CRO feed. During a Dublin software acquisition last quarter, the paid database still showed the previous registered office six weeks after the CRO filing changed it. The CRO entry had already shifted the company into a shared-services address used by four unrelated entities.
That sort of drift matters during pre-LOI screening. Ireland’s Companies Registration Office publishes filings fairly quickly, yet downstream datasets can sit behind for days or longer. Querying the register directly usually exposes the filing sequence the same day it appears.
What the CRO actually returns
The Irish dataset is useful because it exposes filing-level records instead of a heavily normalised company profile. Through OpenRegistry MCP, the Irish tools return raw upstream fields inside jurisdiction_data alongside a unified schema.
For a standard Irish LTD company, get_company_profile usually returns:
- company number
- legal status
- incorporation date
- registered office
- company type
- last annual return date
- next annual return due date
- filing status indicators from the CRO source
The filing metadata tends to matter most during diligence. Irish records often carry CRO-specific labels and references that the legacy paid databases flatten into generic categories.
list_filings is where patterns start showing up. You can walk annual returns, director appointments, office moves, constitution amendments, charge registrations, and capital filings from the same stream.
On distressed targets or companies moving quickly, filing cadence matters more than the summary page. I ran into one case where a burst of B10 director appointments was followed by address changes and charge filings over nine days. Management still described the entity as operationally unchanged during the first diligence call.
Officer data helps with cross-border matching as well. get_officers exposes appointment dates, resignation dates, officer roles, and names exactly as filed upstream. Irish officer formatting is less standardised than GB Companies House records, so direct register access helps when matching directors across Ireland, the UK, or offshore entities.
The CRO does not expose everything.
There is no unrestricted beneficial ownership dataset equivalent to what some diligence teams still expect from older European UBO workflows. Ireland tightened RBO access after the CJEU C-601/20 ruling on public beneficial ownership registers. OpenRegistry does not bypass those restrictions.
Financial statements are uneven too. Filing depth depends on company type and exemptions. Small-company abridged accounts can leave large gaps if you are trying to model operational exposure from registry filings alone.
Filing sequences beat snapshots
A cross-border subsidiary review last month involved an Irish holding company tied to a Dutch financing structure. The aggregator snapshot looked stable. The CRO filings showed a reorganisation already in motion.
Three filings landed within eleven days: a director resignation, a new charge registration, then a constitution amendment. The sell-side materials still described the structure as unchanged.
That sequence changed the risk picture immediately. The financing layer was already shifting before the transaction process formally acknowledged it.
Irish records are useful for spotting these timing gaps because the filing stream is comparatively accessible next to several continental registries.
Charge information is another signal worth watching. If a lender registers a charge shortly before a process starts, it can indicate refinancing pressure or covenant restructuring. You still need the underlying documents to interpret the exposure correctly. Timing alone can change diligence priorities.
Querying the CRO through OpenRegistry MCP
The MCP endpoint connects directly to the registry source. OpenRegistry does not maintain a scoring layer or historical warehouse.
A typical company search looks like this:
{
"tool": "search_companies",
"arguments": {
"jurisdiction": "IE",
"query": "Stripe Payments Europe"
}
}
Once you identify the company number, pull the profile:
{
"tool": "get_company_profile",
"arguments": {
"jurisdiction": "IE",
"company_number": "513174"
}
}
For diligence work, filings are usually the next call:
{
"tool": "list_filings",
"arguments": {
"jurisdiction": "IE",
"company_number": "513174"
}
}
Officer tracing is straightforward:
{
"tool": "get_officers",
"arguments": {
"jurisdiction": "IE",
"company_number": "513174"
}
}
The key detail is field preservation. OpenRegistry keeps the original CRO terminology instead of rewriting everything into a simplified corporate schema. That matters when diligence notes need to match source filing language exactly.
Where the Irish registry still falls short
The CRO works well for operational corporate status checks. Ownership transparency is weaker than many deal teams expect.
You will not get a clean beneficial ownership graph for every Irish-linked structure. AML-gated registers remain restricted. Complex fund structures, nominee arrangements, and layered offshore ownership still require legal work outside registry data.
Historical depth is another limitation. OpenRegistry queries the live register directly and does not store historical snapshots. If you need a point-in-time reconstruction from eighteen months ago, you still need your own archive process or a specialist historical dataset.
Irish filings can also be sparse for smaller private companies. An entity may remain technically compliant while disclosing very little operational detail.
Direct CRO access still catches stale assumptions quickly. Most Irish diligence failures I have seen were timing failures rather than missing-data failures. Someone relied on a downstream cache while the registry had already moved.
OpenRegistry exposes the CRO through MCP at https://openregistry.sophymarine.com/mcp for live registry calls inside diligence tooling or AI workflows.
Top comments (0)