Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@European Financial Filings MCP Server search for Siemens in Germany and show me the top 5 results"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server providing access to European company data and financial filings.
Source | Coverage | Data |
GLEIF | 1.6M+ EU companies | Company search, LEI lookup |
ESEF (filings.xbrl.org) | FR, DK, GB, LT, UA | XBRL financial filings |
UK Companies House | 5M+ UK companies | Filing history, annual accounts |
Curated Lists | DAX40, SIX, FTSE100 | Major index companies |
Related MCP server: SEC EDGAR MCP Server
{
"mcpServers": {
"eu-filings": {
"command": "node",
"args": ["/path/to/eu-filings-mcp-server/build/index.js"],
"env": {
"UK_COMPANIES_HOUSE_API_KEY": "your_api_key_here"
}
}
}
}Variable | Required | Description |
| For UK methods | Free API key from Companies House |
Search 1.6M+ European companies:
{
"method": "search_companies",
"query": "Siemens",
"country": "DE",
"limit": 10
}Supported countries: FR, DE, IT, ES, NL, BE, AT, SE, DK, PL, GB, CH, and more.
{
"method": "get_company_by_lei",
"lei": "YEH5ZCD6E441RHVHD759"
}Get companies with ESEF filings:
{
"method": "get_country_companies",
"country": "FR",
"limit": 10
}Get filings for a company:
{
"method": "get_company_filings",
"lei": "969500YG7U0UQDEHBD60",
"limit": 5
}Extract XBRL financial data:
{
"method": "get_filing_facts",
"filing_id": "23209"
}Requires API key - Get one free at https://developer.company-information.service.gov.uk/
Search UK companies:
{
"method": "search_uk_companies",
"query": "Shell",
"limit": 10
}Get company profile:
{
"method": "get_uk_company_profile",
"company_number": "04366849"
}Get filing history:
{
"method": "get_uk_company_filings",
"company_number": "04366849",
"category": "accounts",
"limit": 10
}Get annual accounts:
{
"method": "get_uk_company_accounts",
"company_number": "04366849",
"limit": 5
}DAX 40 (Germany):
{
"method": "get_dax40_companies"
}FTSE 100 (UK):
{
"method": "get_ftse100_companies"
}SIX (Switzerland):
{
"method": "get_six_listed_companies"
}{
"method": "search_swiss_companies",
"query": "Nestle",
"limit": 5
}{
"method": "get_swiss_company_info",
"lei": "549300U41AUUVOAAOB37"
}Method | Description | Data Source |
| Search companies by name | GLEIF |
| Get company by LEI | GLEIF |
| Get companies with ESEF filings | ESEF |
| Get filing history | ESEF |
| Get entity details | ESEF |
| Extract XBRL data | ESEF |
| Get validation messages | ESEF |
| Filter filing results | ESEF |
| DAX 40 companies | Curated |
| Search Swiss companies | GLEIF |
| Swiss company details | GLEIF |
| SIX listed companies | Curated |
| Search UK companies | UK Companies House |
| UK company profile | UK Companies House |
| UK filing history | UK Companies House |
| UK annual accounts | UK Companies House |
| FTSE 100 companies | Curated |
| Dimensional XBRL facts | ESEF |
| Build fact table | ESEF |
| Search facts by value | ESEF |
| Time series analysis | ESEF |
// 1. Get French companies with filings
{ "method": "get_country_companies", "country": "FR", "limit": 5 }
// 2. Get company details
{ "method": "get_entity_details", "entity_id": "969500YG7U0UQDEHBD60" }
// 3. Get filings
{ "method": "get_company_filings", "lei": "969500YG7U0UQDEHBD60" }
// 4. Extract XBRL financial data
{ "method": "get_filing_facts", "filing_id": "23209" }ESEF Filings: Only available for FR, DK, GB, LT, UA
Germany: No public filing API - use DAX40 list + Bundesanzeiger manual lookup
UK: Requires free API key for Companies House methods
Switzerland: Company metadata only, no XBRL filings (not EU member)
MIT
Unified tool for European financial filings via ESEF (European Single Electronic Format): access company filings, financial statements, and XBRL data from EU regulated markets. Provides comprehensive access to financial reports from 27+ European countries using the filings.xbrl.org API.
| Name | Required | Description | Default |
|---|---|---|---|
| lei | No | For get_company_by_lei, get_company_filings: Legal Entity Identifier (LEI) - 20 character alphanumeric code | |
| limit | No | For search_companies, get_company_filings, get_country_companies, filter_filings: Maximum number of results to return | |
| query | No | For search_companies: Company name to search for (e.g., "LVMH", "Volkswagen", "TotalEnergies") | |
| method | Yes | The operation to perform: search_companies (search EU by name via GLEIF), get_company_by_lei (lookup by LEI), get_company_filings (ESEF filings), search_uk_companies (search UK Companies House), get_uk_company_filings (UK filing history), get_uk_company_accounts (UK annual accounts), get_ftse100_companies (major UK companies) | |
| country | No | For search_companies, get_company_filings, get_country_companies: ISO 3166-1 alpha-2 country code | |
| filings | No | For filter_filings: Array of filing objects to filter | |
| filters | No | For search_facts_by_value: Additional search filters | |
| options | No | For build_fact_table, time_series_analysis: Analysis options | |
| category | No | For get_uk_company_filings: Filter by filing category | |
| end_date | No | For get_company_filings, filter_filings: End date for filing period in YYYY-MM-DD format | |
| entity_id | No | For get_entity_details, get_company_filings: Entity ID from filings.xbrl.org API | |
| filing_id | No | For get_filing_facts, get_filing_validation: Filing ID from filings.xbrl.org | |
| tolerance | No | For build_fact_table, search_facts_by_value: Tolerance range (±) | |
| max_errors | No | For filter_filings: Maximum number of validation errors allowed | |
| start_date | No | For get_company_filings, filter_filings: Start date for filing period in YYYY-MM-DD format | |
| target_value | No | For build_fact_table, search_facts_by_value: Target value to search around | |
| company_number | No | For UK methods: UK Companies House company number (8 characters) | |
| search_criteria | No | For get_dimensional_facts: Search criteria for dimensional facts |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must disclose behavioral traits such as rate limits, pagination, data freshness, or error handling. It only mentions the data source and geographic coverage, omitting any operational behaviors. The description is essentially a high-level capability statement with no caveats or detailed semantics.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise (two sentences) and front-loaded with the core purpose. Some redundancy exists ("European financial filings" vs "EU regulated markets"), but it is not verbose or cluttered. It earns a 4 for clarity without waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (18 parameters, 21 methods, nested objects), the description is too high-level to be complete. It doesn't explain how methods relate, provide example workflows, or set expectations about output formats. The schema helps but doesn't compensate for the lack of practical usage context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and each parameter includes a description listing applicable methods. The tool description adds no parameter-level detail, but the schema already provides sufficient semantics. Baseline 3 is appropriate because the schema carries the burden, and the description doesn't detract.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as a unified access point for European financial filings via ESEF, specifying the resource (company filings, financial statements, XBRL data) and the API source (filings.xbrl.org). It is a specific verb+resource statement, though it doesn't differentiate from siblings (none listed), which is why it doesn't get a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool vs alternatives or how to choose among the 21 methods. The only usage hints are embedded in the schema's parameter descriptions, but the tool description itself offers no direction, prerequisites, or context for method selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
With only one tool, there is no possibility of confusing tools with overlapping purposes. The tool's description clearly states its unified role for European financial filings, leaving no ambiguity.
The single tool name 'eu-filings' is clear and descriptive, using a geographic prefix and resource type. There are no other tools to introduce inconsistency, so the naming is perfectly coherent.
The server covers a very broad domain (EU financial filings across 27+ countries) with only one tool, which feels insufficient. A well-scoped server for this purpose would typically have separate tools for searching, retrieving, and inspecting filings and XBRL data.
The description claims comprehensive access, but the single-tool design leaves uncertainty about whether all necessary operations (e.g., search, filter, download, detail views) are fully covered. It likely handles core retrieval, but any missing operation would be a significant gap.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Company, KYB, VAT, sanctions, LEI and address data for 15 EU countries.
Open financial reference data: companies with LEI/ISIN/FIGI, markets, funds, graph, live series.
French & European company registry for AI agents: KYB, sanctions, annual accounts. x402, no API key.
UK company data: profiles, iXBRL financials, directors, PSC chains, ECCTA. Hosted, no key.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/openpharma-org/eu-filings-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
