Instantly query European financial data for AI. This FastMCP server connects the FinancialReports.eu API to powerful language models, making complex
Instantly query European financial data for AI. This FastMCP server connects the FinancialReports.eu API to powerful language models, making complex reports easy to search, analyze, and explain. The financial reports mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.
An MCP (Model Context Protocol) server for accessing the Financial Reports API, providing tools and resources to access company financial filings, industry classifications, and related data.
Everything the assistant can do here goes through one of these:
Prompts — The Prompts tool exposed by this serverLogs — When running directly, logs are output to the console. For Docker, you can view logs with:You will need one environment variable: API_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Financial Reports's toolset — Prompts, Logs — is a fair guide to whether it matches your workflow. It is maintained by itisaevalex; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Prompts | The Prompts tool exposed by this server. |
| Logs | When running directly, logs are output to the console. For Docker, you can view logs with: |
{
"mcpServers": {
"financial-reports": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e", "API_KEY=your_api_key_here",
"-e", "API_BASE_URL=https://api.financialreports.eu/",
"-e", "MCP_TRANSPORT=stdio",
"financial-reports-mcp:latest"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.