DACH Tech-Stack Hiring Signals + MCP

Detect DACH companies that are currently hiring for specific technologies and use those public job postings as a compact B2B buying-intent signal.

This Actor can run in two ways:

• Normal Apify run: writes signal/job rows to the dataset and a RUN_SUMMARY record to Key-Value Store.
• Standby MCP server: exposes search_hiring_signals, get_company_jobs, and list_top_signals to Claude, Cursor, VS Code, n8n, and other MCP-compatible clients.

The default input is a small direct dataset run, not MCP server mode. This keeps Apify Store health checks fast, cheap, and non-empty. Use mode: "mcp_server" or the Standby URL when you want agent access.

What You Get

• DACH company-level hiring signals from a curated directory of 13 live-checked companies
• Technology detection for Salesforce, Kubernetes, Snowflake, AWS, SAP, dbt, Terraform, React, Python, and more
• Stable signalId and recordHash fields for scheduled monitoring
• Job-level rows for single-company lookups
• Source links to public Greenhouse job boards
• RUN_SUMMARY with status, source counts, warning/error details, and result counts
• MCP tools for agent workflows

Default Run

{
  "mode": "list_top_signals",
  "country": "DE",
  "maxResults": 5,
  "testMode": true,
  "maxCompanies": 5,
  "concurrency": 3,
  "maxRetries": 2,
  "requestTimeoutSecs": 15
}

The default scans a stable German subset and returns signal rows plus one summary row.

Direct Run Examples

Search for Kubernetes hiring signals

{
  "mode": "search_hiring_signals",
  "technology": "Kubernetes",
  "country": "DE",
  "maxResults": 10,
  "testMode": false,
  "maxCompanies": 15
}

Get all public jobs for one company

{
  "mode": "get_company_jobs",
  "companyName": "N26",
  "testMode": false
}

List strongest DACH hiring signals

{
  "mode": "list_top_signals",
  "country": "all",
  "maxResults": 20,
  "testMode": false,
  "maxCompanies": 13
}

Output

Signal rows:

{
  "recordType": "HIRING_SIGNAL",
  "signalId": "search_hiring_signals:n26.com:kubernetes",
  "recordHash": "b62...",
  "runMode": "search_hiring_signals",
  "targetTechnology": "Kubernetes",
  "companyName": "N26",
  "companyDomain": "n26.com",
  "country": "DE",
  "detectedTechnologies": ["AWS", "Kubernetes", "Terraform"],
  "signalStrength": 80,
  "openRoleCount": 66,
  "matchingJobCount": 4,
  "keyJobTitles": ["Senior Platform Engineer"],
  "sourceUrls": ["https://boards.greenhouse.io/n26"],
  "scrapedAt": "2026-07-03T12:00:00.000Z"
}

Summary row and KVS record:

{
  "recordType": "RUN_SUMMARY",
  "status": "SUCCEEDED",
  "mode": "list_top_signals",
  "country": "DE",
  "testMode": true,
  "companiesPlanned": 5,
  "sourcesPlanned": 5,
  "sourceSuccessCount": 5,
  "sourceFailureCount": 0,
  "postingsScanned": 120,
  "recordsReturned": 5,
  "warnings": [],
  "errors": []
}

Summary statuses:

• SUCCEEDED: valid source data was fetched and rows were returned
• NO_RESULTS: valid source data was fetched, but no row matched the filter
• PARTIAL_SOURCE_FAILURE: at least one source failed, but valid data was still returned from another source
• FAILED: input was invalid or no valid source data could be verified

MCP Usage

Standby/MCP endpoint:

https://actorpilot--tech-stack-hiring-signal-monitor.apify.actor/mcp?token=YOUR_APIFY_API_TOKEN

Example MCP client configuration:

{
  "mcpServers": {
    "dach-hiring-signals": {
      "url": "https://actorpilot--tech-stack-hiring-signal-monitor.apify.actor/mcp?token=YOUR_APIFY_API_TOKEN"
    }
  }
}

Available MCP tools:

• search_hiring_signals
• get_company_jobs
• list_top_signals

Data Sources And Limits

Current directory:

• 13 curated DACH companies with live-checked sources
• Germany, Austria, Switzerland
• Active sources in the current directory: Greenhouse
• Lever and Personio parsers are implemented, but the current curated directory only keeps sources that were live at the last verification

Limits:

• This is not a complete DACH company database.
• It returns public job-posting signals, not contact data.
• Country is based on the company directory classification, not every job location.
• Technology detection is deterministic keyword matching and can miss synonyms.
• Broad job scrapers cover more ATS platforms; this Actor is optimized for compact DACH account-level signals and MCP workflows.

Recommended Workflows

Weekly DACH sales signal monitor

1. Run search_hiring_signals for your target stack.
2. Export rows where recordType is HIRING_SIGNAL.
3. Compare signalId and recordHash across scheduled runs.
4. Trigger an Apify webhook when a new signal appears or a hash changes.

Account research before outreach

1. Run get_company_jobs for a target account.
2. Review detected technologies and job titles.
3. Use source URLs to verify current hiring context before contacting the account.

Agent workflow

Connect the MCP endpoint and ask:

Which German companies are hiring for Kubernetes right now?
Show me the top DACH companies by tech hiring signal.
Get open jobs and detected stack for N26.

Troubleshooting

Default run returned no signals

Check the RUN_SUMMARY row. If status is NO_RESULTS, sources responded but no signals matched. Turn off testMode, increase maxCompanies, or lower your filter strictness.

The run failed

The Actor fails intentionally for invalid input or when no source data can be verified. This avoids false-positive monitoring runs.

MCP mode exits after being idle

That is expected. The server exits after a short idle period to keep compute cost low. Standby will start it again when needed.