Signaliz

What is Signaliz MCP? Signaliz MCP is a B2B go-to-market (GTM) intelligence and enrichment MCP server that exposes 60+ Signaliz API capabilities for verified lead generation, email verification, company and people enrichment, GTM automation (Ops Routines), app actions, and workspace controls. It is a public distribution manifest and indexable tool schema for Signaliz’s hosted MCP service.

How to use Signaliz MCP?

• Hosted endpoint: https://api.signaliz.com/functions/v1/signaliz-mcp
• Authenticate with a Signaliz API key (query param or Authorization: Bearer) or via OAuth where supported.
• Quick start: create an API key in Signaliz Settings > Developer > API Access and call the endpoint with ?api_key=YOUR_API_KEY or send as a Bearer token.
• For local stdio MCP clients, install the npm bridge: npx -y @signaliz/mcp-server (example: claude mcp add signaliz -e SIGNALIZ_API_KEY=sk_your_key – npx -y @signaliz/mcp-server) and configure clients (Claude Desktop, Cursor, etc.) to run the bridge.
• Use tools listed in tools/tools.json or query list_capabilities to discover available tool schemas and costs.

Key features

• Verified email finding and deliverability verification (single and batch).
• Person and company discovery, enrichment, and structured signal research (hiring, funding, product launches, leadership changes, etc.).
• Batch job support for large lists (up to ~5,000 items) with job_id + check_job_status or callback webhooks.
• Ops Routines (agentic, scheduled routines) with chaining, streaming SSE results, approvals, feedback, and event wake triggers.
• Custom AI prompts over records with structured outputs and model selection.
• Generic HTTP executor for calling external APIs and app connectors to discover and execute actions across CRM/marketing/productivity stacks.
• Workspace controls: budgets, blocklists, ICPs, campaign books, audit trail, agent memory, and analytics.

Typical use cases

1. Building verified outreach lists and performing mass or one-off email verification.
2. Enriching accounts and leads with real-time company signals for prioritization and playbooks.
3. Orchestrating autonomous GTM workflows (Ops Routines) that run on schedules or events and stream results to webhooks or pipelines.
4. Integrating Signaliz actions into CRMs and marketing systems via discovered connectors and execute_connection_action.
5. Running custom AI-based enrichment and structured extraction across datasets.

FAQ

• Q: How do batch jobs work? A: Batch tools return a job_id immediately; poll check_job_status or provide callback_url (and callback_secret) to receive a webhook on completion.

• Q: What output formats are supported? A: Tools accept output_format = “json” or “markdown”. Use json for structured downstream processing.

• Q: How is authentication handled? A: API Key via query param or Authorization header; OAuth discovery is supported for clients that implement it.

• Q: Is there a local bridge for stdio clients? A: Yes — use the npm bridge @signaliz/mcp-server (npx -y @signaliz/mcp-server) and set SIGNALIZ_API_KEY in the environment.

• Q: Are there usage limits or costs? A: Plans include varying monthly GTM credits; metered provider-backed actions (email verification, discovery, enrichment) consume credits. Signaliz focuses on accuracy and governed credit usage rather than unlimited-volume access.

• Q: Can Signaliz mutate external systems? A: Read-only enrichment is safe; tools that upload data, run systems, connect apps, execute actions, or approve/modify workspace resources can change systems and should be used with approval controls.

• Q: Where can I find the tool index and schemas? A: The full indexable tool schema is in tools/tools.json in the repo and is generated from the @signaliz/mcp-server tools/list response.

Useful links: Homepage https://signaliz.com, NPM @signaliz/mcp-server, repo https://github.com/signaliz/signaliz-mcp, hosted MCP endpoint https://api.signaliz.com/functions/v1/signaliz-mcp.