$5 free Limited time. Sign up to activate. Get your $5 →
Coming soon · Use case

Back an MCP-native lead database with a licensed people feed

The trigger, the steps and the outcome, for when it opens. It is not live yet.

Not live yet. We will email you when it opens.

The job
Let a lead-database product answer agent and assistant queries (via MCP) from its own index of people and companies, enriching contact details only for rows the user keeps.
When
A lead-database vendor rebuilds its product for AI assistants and needs an index it controls rather than per-query lookups.
Outcome
Agency and sales users build large, clean lists from inside an assistant.

How the data flows

2 inputs → People data feed + Company data feed + Work emails + Personal emails → 4 fields sample data
01 · Inputs
Search
VP Revenue Operations · San Francisco, CA
Client ICP
Founders · e-commerce brands · US
02 · Forager
People data feed + Company data feed + Work emails + Personal emails
Match found
03 · Outputs
Jane ExampleVP Revenue Operations · Example Inc.
work email
jane@example.com
personal email
jane.e@example.net
name
Jane Example
title
VP Revenue Operations
mobile
+1 (415) 555-0142
company
Example Inc.
4 fields in the responseexample data

Steps

  1. Ingest people_feed and company_feed into the product's search index on each delivery
  2. Expose search, filter and count tools over MCP so assistants can build lists conversationally
  3. Enrich only selected rows with /person_contacts_lookup/work_emails/ and /person_contacts_lookup/personal_emails/
  4. Return lists with credits used and log query-to-export conversion

Inputs and outputs

InputsOutputs
assistant querypeople list
ICP filterscompany list
work_email
personal_email
Coming soon

Join the waitlist

Nothing here is live yet. Leave your work email and we will write when it opens.

1. Your work emailWe fill in your name and company from it.

2. A few details

We email you when it opens. No date yet.