DACH Business Intelligence MCP Server avatar

DACH Business Intelligence MCP Server

Pricing

Pay per usage

Go to Apify Store
DACH Business Intelligence MCP Server

DACH Business Intelligence MCP Server

DACH business intelligence MCP server for AI agents. Search the German Handelsregister, monitor EU tenders from TED, and generate structured company research. Works with Claude, Codex, Cursor, VS Code, n8n, LangChain, OpenAI Agents SDK, Gemini, and other MCP clients.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

S. Klein

S. Klein

Maintained by Community

Actor stats

1

Bookmarked

1

Total users

0

Monthly active users

3 days ago

Last modified

Share

Give your AI agent structured access to German company register data and EU public tenders — in one MCP server, one connection, three tool calls.

Instead of manually browsing Handelsregister.de or TED procurement portals, your agent calls search_company_register, search_eu_tenders, or research_company and gets clean JSON back in seconds. No browser automation. No fragmented portals. No expensive data contracts.

Works with Claude, Cursor, VS Code, n8n, LangChain, OpenAI Agents SDK, Gemini, and any MCP-compatible client.


Quick Connect

MCP endpoint

Use this remote MCP server URL:

https://actorpilot--dach-business-intelligence-mcp.apify.actor/mcp?token=YOUR_APIFY_API_TOKEN

Replace YOUR_APIFY_API_TOKEN with your token from Apify API & Integrations.

Copy-paste prompt for AI tools that can set up MCP for you

If your AI assistant can manage MCP configuration, paste this:

Please connect this remote MCP server for me.
Name: dach-bi
Transport: Streamable HTTP
URL: https://actorpilot--dach-business-intelligence-mcp.apify.actor/mcp?token=YOUR_APIFY_API_TOKEN
After setup, verify that these tools are available:
- search_company_register
- search_eu_tenders
- research_company

Important: use the MCP endpoint URL above, not the normal Apify Actor page URL. A link like https://apify.com/actorpilot/... is the product page, not the MCP transport endpoint.

Works with

  • Claude
  • Codex
  • Cursor
  • VS Code
  • Windsurf
  • Zed
  • n8n
  • LangChain / LangGraph
  • OpenAI Agents SDK
  • Google Gemini / Vertex AI
  • Any MCP client that supports remote Streamable HTTP

Why use this instead of individual tools

If you only need one data source, use the individual Actors:

This MCP Server is the right choice when your agent workflow needs both in a single session:

ScenarioWhat happens
Due diligence on a supplierAgent calls search_company_register → confirms legal status → calls search_eu_tenders → checks if supplier wins public contracts → calls research_company → returns combined profile
Lead research for a consulting firmAgent identifies a prospect → verifies register data → surfaces open tenders in their sector → generates first-pass research packet
Compliance checkAgent confirms counterparty registration, legal form, and authorised representatives in a single research_company call

ROI context: Bloomberg ESG and Refinitiv company data start at €10,000+/year. This MCP server costs $0.05 per tool call.


What this MCP server does

This MCP server acts as a structured gateway between your AI agent and authoritative DACH business data sources. Instead of browsing fragmented government portals or scraping inconsistent pages, your agent calls a tool and receives structured JSON ready for analysis, summarization, enrichment, or downstream automation.

Data sources covered

  • Handelsregister - Official German commercial register. Returns registered address, legal form, register number, register court, business purpose, and current decision-makers.
  • TED (Tenders Electronic Daily) - Official EU public procurement platform. Returns tenders with authority, dates, country, and source links.
  • Company Research Aggregator - Combines register data and tender data into one structured company profile.

Best fit for

  • AI developers building business research agents
  • VC and PE teams automating deal screening
  • Consultancies doing rapid market and company profiling
  • Procurement teams monitoring TED opportunities
  • Compliance and legal teams checking counterparties

Typical use cases

  • Due diligence and KYC - Verify whether a company is registered and who is authorized to represent it.
  • Lead research - Enrich CRM and outbound workflows with official company information.
  • Tender monitoring - Track public procurement opportunities by keyword and country.
  • Company profiling - Generate first-pass research packets for consulting, VC, PE, and M&A workflows.

Available MCP tools

search_company_register

Search the official German Handelsregister by company name or register number.

Typical inputs

ParameterTypeDescription
companyNamestringCompany name, for example SAP SE
registerNumberstringRegister number, for example HRB 719782
registerCourtstringRegister court, for example Mannheim
registerTypeenumHRB, HRA, GnR, PR, VR, or all
maxResultsintegerResult limit from 1 to 20

search_eu_tenders

Search TED procurement notices by keyword, country, CPV code, or minimum value.

Typical inputs

ParameterTypeDescription
searchPhrasestringSearch keyword, for example IT services
countrystringISO3 country code such as DEU, AUT, CHE
cpvCodestringCPV code such as 72000000
minValueEurnumberMinimum estimated value in EUR
maxResultsintegerResult limit from 1 to 50

research_company

Run combined company research in a single call by aggregating register data and tender data.

Typical inputs

ParameterTypeDescription
companyNamestringCompany name to research
includeSourcesarrayOne or both of register and tenders

How to connect your AI agent

Claude

Add the MCP server URL from the Quick Connect section to your Claude MCP or custom connector setup.

Use this endpoint:

https://actorpilot--dach-business-intelligence-mcp.apify.actor/mcp?token=YOUR_APIFY_API_TOKEN

If your Claude client supports natural-language setup through another agent, use the copy-paste prompt from Quick Connect.

Codex and other coding agents

Some coding agents can edit MCP configuration for you. Paste this:

Please add this remote MCP server to my MCP configuration.
Server name: dach-bi
Transport: Streamable HTTP
URL: https://actorpilot--dach-business-intelligence-mcp.apify.actor/mcp?token=YOUR_APIFY_API_TOKEN
Then verify that these tools are available:
- search_company_register
- search_eu_tenders
- research_company

Cursor, VS Code, Windsurf, Zed

Use a config like this:

{
"mcpServers": {
"dach-bi": {
"url": "https://actorpilot--dach-business-intelligence-mcp.apify.actor/mcp?token=YOUR_APIFY_API_TOKEN"
}
}
}

If your client supports header-based auth, you can also use:

{
"mcpServers": {
"dach-bi": {
"url": "https://actorpilot--dach-business-intelligence-mcp.apify.actor/mcp",
"headers": {
"Authorization": "Bearer YOUR_APIFY_API_TOKEN"
}
}
}
}

n8n

  1. Add an MCP Client node
  2. Choose remote MCP or Streamable HTTP transport if available
  3. Set the URL to https://actorpilot--dach-business-intelligence-mcp.apify.actor/mcp?token=YOUR_APIFY_API_TOKEN
  4. Let n8n discover the tools
  5. Connect it to your AI Agent node

LangChain, LangGraph, OpenAI Agents SDK, Gemini, custom apps

Point your remote MCP client to:

https://actorpilot--dach-business-intelligence-mcp.apify.actor/mcp?token=YOUR_APIFY_API_TOKEN

This server uses Streamable HTTP for MCP requests.


Example tool calls

{
"name": "search_company_register",
"arguments": {
"companyName": "SAP SE",
"registerCourt": "Mannheim",
"maxResults": 1
}
}
{
"name": "search_eu_tenders",
"arguments": {
"searchPhrase": "IT services",
"country": "DEU",
"maxResults": 5
}
}

Example: full company research

{
"name": "research_company",
"arguments": {
"companyName": "Siemens AG",
"includeSources": ["register", "tenders"]
}
}

Output reference

search_company_register returns fields such as

  • companyName
  • legalForm
  • registerNumber
  • registerCourt
  • address
  • businessPurpose
  • decisionMakers
  • sourceUrl
  • scrapedAt

search_eu_tenders returns fields such as

  • noticeId
  • title
  • contractingAuthority
  • country
  • publicationDate
  • deadline
  • estimatedValueEur
  • cpvCodes
  • description
  • sourceUrl
  • scrapedAt

research_company returns fields such as

  • companyName
  • sourcesQueried
  • registerData
  • euTenders
  • summary
  • errors
  • scrapedAt

Pricing

This Actor uses Pay Per Event pricing. You are charged per successful tool call, not per server start.

EventPrice
search_company_register$0.05 per call
search_eu_tenders$0.05 per call
research_company$0.05 per call

Typical usage patterns:

  • 100 company lookups per day -> about $150 per month
  • 20 due diligence reports per day -> about $30 per month
  • 50 tender monitoring checks per day -> about $75 per month

FAQ

Does this use only public data?

Yes. The data comes from public registries and public procurement sources such as the German Handelsregister and TED.

Which countries are covered?

Primary register coverage is Germany. Tender coverage includes Germany, Austria, Switzerland, and broader EU TED search results depending on the query.

How fast are the responses?

Typical response times:

  • search_company_register: about 8 to 15 seconds
  • search_eu_tenders: about 5 to 12 seconds
  • research_company: about 12 to 25 seconds

What happens if no company is found?

The tool returns a structured result or an empty result set instead of crashing your workflow.

Can I test the MCP server directly before connecting it to an agent?

Yes. Open:

https://actorpilot--dach-business-intelligence-mcp.apify.actor/openapi.json?token=YOUR_APIFY_API_TOKEN

You can also send MCP requests directly to:

https://actorpilot--dach-business-intelligence-mcp.apify.actor/mcp?token=YOUR_APIFY_API_TOKEN

How long does a research_company call take?

Typical response times:

  • search_company_register: 8–15 seconds
  • search_eu_tenders: 5–12 seconds
  • research_company (both sources): 12–25 seconds

These times reflect live data retrieval. The server does not cache results.

Can I use this in an automated n8n or LangGraph workflow?

Yes. Point your MCP client at the Streamable HTTP endpoint. In n8n, use the MCP Client node. In LangGraph or LangChain, use any MCP-compatible client library. The server handles session management and returns structured JSON on every call.


Support

Found a bug or want another DACH data source integrated? Open an issue on the Actor page or contact us through Apify.

Planned future extensions:

  • Bundesanzeiger filings
  • Kununu employer reviews
  • StepStone job postings
  • Broader multi-source research aggregation