All tools
LushaL

by Lusha

Get a company's buying signals

Returns recent signals for companies found by name or domain, such as headcount growth, hiring surges, website traffic changes and news like funding rounds or executive hires.

View on GitHub
Updated Sep 27, 2026Available asMCP

Description

List the valid signal types first with `signals_company_filters`, which costs no credits. Signals cover the last six months by default, and each signal returned costs credits, so run it on a shortlist. For companies you already have Lusha IDs for, use `signals_companies_get`.

get-company-signals.md

Get a company's buying signals

Returns recent signals for companies found by name or domain, such as headcount growth, hiring surges, website traffic changes and news like funding rounds or executive hires.

List the valid signal types first with signals_company_filters, which costs no credits. Signals cover the last six months by default, and each signal returned costs credits, so run it on a shortlist. For companies you already have Lusha IDs for, use signals_companies_get.

Set up

Use the first option your agent supports.

MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "lusha": { "url": "https://mcp.lusha.com" } } }

Call the MCP tool signals_companies_search.

Server URL: https://mcp.lusha.com

Before doing anything else, make one read-only call to confirm access.

Rules

  • Ask the user before anything that sends messages, costs money, or changes data.
  • Never print API keys.

Built from these files in the repository

The layout and the rules come from lib/catalog/render-markdown.ts, the set-up wording from lib/catalog/render-access.ts.

Ways in

RouteSourceCallRequiredDocs
MCPOfficial · remotesignals_companies_searchOAuthDocs

Workflows using Get a company's buying signals

No workflows yet
No published workflow uses Get a company's buying signals yet.