The signal layer for event triggered Yalc workflows. When intent (hiring, funding, news, technographics) drives outbound timing, this MCP fires the trigger.
claude mcp add predictleads --transport http "https://mcp.predictleads.com/sse" --headers "X-API-Key:YOUR_PREDICTLEADS_KEY"
Sign up at predictleads.com (100 free API requests per month). Generate an API key from your dashboard. Predictleads documents an MCP integration; the exact server URL may differ from the placeholder above. Check the MCP integration section of the Predictleads docs for the current URL and headers.
Predictleads provides structured signal data on 100 million plus companies: news events across 29 categories, job openings, technographics (1.2 billion technology detections all time), key customers, financing rounds, and similar company lookups. The vendor positions explicitly for AI agents and exposes the same dataset via REST, MCP, webhooks, and flat files.
For Yalc workflows, Predictleads is the canonical signal source. Where Crustdata gives you the database (who exists), Predictleads gives you the trigger (what just changed). When a Yalc agent says "alert me when ICP accounts post a hiring signal" or "trigger outbound when a target company raises Series B", Predictleads supplies the event.
The Predictleads MCP sits at the **listen** node in Yalc's GTM topology. Most static prospecting (firmographics, ICP filtering) happens upstream in Crustdata. Predictleads kicks in when the question shifts from "who matches" to "who just changed".
The MCP exposes the signal endpoints as native Claude tools. Yalc workflows can subscribe to Predictleads webhooks for real time push, or query the MCP on demand for batch intelligence digests.
The signal listener. Yalc subscribes to Predictleads watchers on target accounts, classifies the event via Claude, decides whether to trigger an outbound action. Downstream is the standard Yalc send pipeline.
Copy paste prompts for Claude Code that invoke the Predictleads MCP.
Predictleads documents an MCP integration that works inside Claude Code, Cursor, and other MCP clients. The free tier (100 requests per month) is enough to pilot a real Yalc workflow. Webhooks are first class for production volume.
They compose. Crustdata is a database (who exists, where, what they do). Predictleads is a signal layer (what just changed). Most Yalc workflows install both and chain them.
29 event categories. High signal include financing rounds, executive hires, expansion moves, technology adoption, hiring patterns, layoff news, product launches. Lower signal include routine press releases.
Yes. Webhooks are first class. Subscribe to event types and target accounts, Predictleads POSTs when events match. Yalc workflows route POSTs through Claude for classification before any action.
Most events surface within hours of detection. Some (job openings, news) are near real time. Some (financing rounds) lag because the source itself lags.
It's company centric. For person level, pair with Crustdata or Apollo. The strength is company events and technographics.
Yes for piloting. 100 requests per month with webhook delivery scales further than 100 polling calls. For low frequency monitoring on a small target list, the free tier covers a real workflow.
Drop it into Claude Code and orchestrate from your next Yalc prompt.
claude mcp add predictleads --transport http "https://mcp.predictleads.com/sse" --headers "X-API-Key:YOUR_PREDICTLEADS_KEY"