list_filingsCompany filing history with normalised categories (accounts, annual-return, officers, PSC, charges) + optional document_id round-trip.
Return the filing history for a company, newest first. Each filing has filing_id, filing_date, category (normalised across jurisdictions), description, and (where upstream exposes one) a document_id that round-trips to get_document_metadata / fetch_document. Filter by category to narrow.
| Name | Type | Required | Description |
|---|---|---|---|
jurisdiction | string | yes | ISO code. Currently: GB, IE, FI, CA, IS, PL, DE, NZ, NL, MC, ES, KR, MX, RU, IM, LI. |
company_id | string | yes | Registry-specific ID. |
category | string | no | Filter: accounts / annual-return / officers / persons-with-significant-control / charges / resolution / confirmation-statement / … |
limit | integer | no | Page size (default 25, max 1000). |
curl -sL https://openregistry.sophymarine.com/mcp \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_filings","arguments":{"jurisdiction":"GB","company_id":"08804411","limit":5}}}'
CA - Canada (federal)CY - CyprusES - SpainFI - FinlandGB - United KingdomHR - CroatiaIE - IrelandIM - Isle of ManIS - IcelandJP - JapanKR - South KoreaLI - LiechtensteinMC - MonacoMX - MexicoNL - NetherlandsNZ - New ZealandPL - PolandRU - RussiaSE - Swedenaccounts / annual-return / confirmation-statement / officers / persons-with-significant-control / charges / resolution / capital / incorporation / dissolution. The category field is normalized across jurisdictions. The registry's native form code stays under jurisdiction_data.form_type for round-tripping.
Just metadata + a document_id. To download, pipe document_id into fetch_document (or get_document_metadata first to check format / size). For annual accounts specifically, get_financials is the more ergonomic shortcut — same data, period-end-sorted.
Pre-electronic filings (paper) often have a filing record but no scanned PDF on the registry server. has_document tells you upfront whether a fetch is possible. Pre-2003 GB filings, pre-1997 IE filings, and most Eastern European pre-2010 filings frequently lack downloads.
limit caps at 1000 per call. For larger histories, jurisdiction_data.next_cursor (where the registry exposes one) returns a token to pass on the next call. Some registries cap total history at 35 years — older filings simply not returned.
filing_date is YYYY-MM-DD ISO. Always reflects the date the registry RECEIVED the filing, NOT the period the filing covers. For period-end (e.g. accounts cover FY2024 ending 2024-12-31), look inside the filing's payload via fetch_document or use get_financials which surfaces period_end as a top-level field.
Newest first, always. To get oldest, fetch all and reverse client-side, or paginate to the last page (jurisdiction_data.total_count / your limit). Some registries return chronological order in their native API; we normalize.
Yes — annual accounts can be filed, then re-filed (corrections, late amendments). Both records remain. description on the later filing usually contains 'AA', 'AMD', or similar amendment marker. Use the most recent for the canonical view; preserve the older ones for audit trail.
list_filings(category='charges') gives the filing events (MR01, MR04 etc.). get_charges gives the structured charge register snapshot (active + satisfied charges with creator, secured party, amount). Use get_charges for current-state, list_filings for the event log.
Currently supported: GB, IE, FI, CA, IS, PL, DE, NZ, NL, MC, ES, KR, MX, RU, IM, LI. Others return 501 + alternative_url. The list expands as we wire each registry's filing endpoint. Check list_jurisdictions({supports_tool: 'list_filings'}) for live coverage.
Not via parameters — list_filings doesn't accept date_from / date_to. Fetch newest-first with a high limit, then filter client-side. For very long histories where date filtering would matter most (GB Tesco, decades of filings), it's quicker to filter by category first.