The claim it makes about its own output is the useful one: every retained result is dated and source-backed, and it returns fewer results rather than filling the quota — which is the opposite of how most prospecting data behaves. The chain is what you are buying: a signal question produces companies, a company produces a person and a verified address, and the same signal produces the copy that references it. Everything metered runs on credits, so a broad query is a spend, and the flow status tool exists precisely because reading a result should not cost another one.
A B2B go-to-market server: signal discovery from an open-ended question, contact email finding and verification, ongoing monitoring of named companies, and outreach copy written from a specific signal.
- Up to 100 distinct companies found from a natural-language signal question, each result dated and source-backed, with fewer returned rather than padded
- One company's newest signals by domain — the newest distinct dated developments over a lookback window you can set, with your own research prompt if you want to steer it
- The highest-confidence work email for a person from a LinkedIn profile URL alone, or from a name plus company domain
- Deliverability verification for one email, or up to 5,000 submitted together, returning status, catch-all state, credits charged and whether it is safe to send
- Durable monitors on companies that run on a schedule or on demand and return verified signal rows, created one at a time or in bulk, with duplicate and invalid domains reported instead of silently created
- Monitor management: list with schedule and next run, update, pause and resume, run now with an idempotency key that returns the original run if reused, delete, and export the monitored companies and their signals
- Delivery configured per workspace — CSV only or webhook — with a test event you can fire at an HTTPS endpoint before relying on it
- One grounded signal turned into three complete personalized emails, or drafted from firmographic context when there is no signal to work from
- A single flow from signal question to review-ready outreach drafts, and a status receipt for an existing run that starts no new work and spends nothing
- Batch work returned as a job id, with bounded result pages fetched back afterwards
- Every tool accepting an output format, markdown or json, so another agent or script can consume the result
A Signaliz account and an API key, created from Settings > Developer > API Access. The hosted endpoint is https://api.signaliz.com/functions/v1/signaliz-mcp over Streamable HTTP: pass the key as an Authorization: Bearer header, or as an api_key query parameter for clients that cannot send headers, and clients that support MCP remote OAuth can use the protected-resource metadata the server advertises. For stdio clients there is a local bridge — npx -y @signaliz/mcp-server with SIGNALIZ_API_KEY set. Usage is metered: plans include a monthly allowance of GTM credits, and the provider-backed actions — email verification, discovery, signal enrichment, monitoring, custom prompts — draw on it. This repository is the public distribution manifest; the server itself is hosted by Signaliz.
One command plus a key — claude mcp add signaliz -e SIGNALIZ_API_KEY=sk_your_key -- npx -y @signaliz/mcp-server, then supply credentials