DACH Business Intelligence MCP

Use one Apify Actor as either:

• a remote MCP server for AI agents, or
• a normal Apify dataset run for quick checks and API workflows.

The Actor exposes German company-register lookup, EU TED tender search, and a combined company research tool. The default run is a cheap health check that writes a dataset row and RUN_SUMMARY, so Apify Store tests do not wait for an idle MCP server.

What You Get

• MCP tools for Claude, Cursor, VS Code, n8n, LangChain, OpenAI Agents SDK, and other Streamable HTTP MCP clients
• Direct Apify modes for health checks, company-register search, tender search, and company research
• Dataset rows with recordType, recordId, recordHash, source URLs, timestamps, and a RUN_SUMMARY
• Key-Value Store records: RUN_SUMMARY and OUTPUT
• OpenAPI metadata at /openapi.json
• Graceful idle shutdown for MCP server runs

Default Run

{
  "mode": "health_check"
}

The default does not call external data sources. It verifies that the Actor can start, lists the available MCP tools, and writes:

• one MCP_SERVER_HEALTH dataset row
• one RUN_SUMMARY dataset row
• RUN_SUMMARY and OUTPUT records in Key-Value Store

Direct Run Examples

Search German Company Register

{
  "mode": "search_company_register",
  "companyName": "SAP SE",
  "registerCourt": "Mannheim",
  "maxResults": 1
}

Search EU Tenders

{
  "mode": "search_eu_tenders",
  "searchPhrase": "IT services",
  "country": "DEU",
  "maxResults": 5
}

Combined Company Research

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

MCP Usage

Use this remote MCP endpoint:

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

Use the MCP endpoint, not the normal Apify Store page URL.

Example MCP client configuration:

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

Available MCP tools:

• search_company_register
• search_eu_tenders
• research_company

Root health endpoint:

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

OpenAPI endpoint:

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

Output Records

Health check row

{
  "recordType": "MCP_SERVER_HEALTH",
  "recordId": "mcp-health:dach-business-intelligence-mcp",
  "status": "ok",
  "toolsAvailable": ["search_company_register", "search_eu_tenders", "research_company"],
  "mcpPath": "/mcp",
  "openapiPath": "/openapi.json",
  "checkedAt": "2026-07-03T12:00:00.000Z"
}

Register rows

{
  "recordType": "REGISTER_RESULT",
  "recordId": "register:mannheim:hrb 719782",
  "companyName": "SAP SE",
  "legalForm": "SE",
  "registerNumber": "HRB 719782",
  "registerCourt": "Mannheim",
  "address": {
    "street": null,
    "city": "Walldorf",
    "postalCode": null
  },
  "sourceUrl": "https://www.handelsregister.de/...",
  "scrapedAt": "2026-07-03T12:00:00.000Z"
}

Tender rows

{
  "recordType": "TENDER_RESULT",
  "noticeId": "2026/S 001-000001",
  "title": "IT services",
  "contractingAuthority": "Example Authority",
  "country": "DEU",
  "publicationDate": "2026-07-03",
  "deadline": null,
  "estimatedValueEur": null,
  "cpvCodes": ["72000000"],
  "sourceUrl": "https://ted.europa.eu/..."
}

Run summary

{
  "recordType": "RUN_SUMMARY",
  "status": "SUCCEEDED",
  "mode": "health_check",
  "recordsReturned": 1,
  "warnings": [],
  "errors": []
}

Summary statuses:

• SUCCEEDED: valid data or health metadata was returned.
• NO_RESULTS: the request was valid, sources responded, but no matching business data was found.
• PARTIAL_SOURCE_FAILURE: at least one selected source failed, but another returned valid data.
• FAILED: input was invalid or no selected source could return verifiable data.

Pricing

The MCP data tools use Pay Per Event pricing:

Event	Price
tool-call	$0.05 per successful data tool call

The default health_check mode does not call sub-actors and is intended for Store health checks and integration smoke tests.

Best Use Cases

• AI agents that need company and tender context in one MCP session
• Due diligence workflows for German companies
• Tender monitoring by keyword, country, CPV code, or estimated value
• CRM or lead research where structured JSON is needed
• n8n, LangGraph, or custom agent workflows that need a remote MCP server

Limitations

• German register coverage depends on the underlying Handelsregister Actor and public source availability.
• TED search depends on the underlying TED Procurement Radar Actor and current TED API/source behavior.
• This Actor does not cache across separate Actor runs.
• Direct runs are useful for API and dataset workflows, but MCP clients should use the Standby endpoint.
• The Actor returns public business data, not private contact data.

Troubleshooting

Default run returns only health data

That is expected. Choose a direct data mode or connect via MCP to retrieve company/register/tender data.

MCP client cannot connect

Check that you are using /mcp?token=YOUR_APIFY_API_TOKEN, not the Apify Store page URL.

A data mode returns no results

Check RUN_SUMMARY.status. NO_RESULTS means the request was valid but no matching records were found. FAILED means the input or all selected sources failed.

MCP server exits after being idle

That is expected. Standby starts it again when a new request arrives.