MCP Server
MCP tools
The nine LeadX tools an AI assistant can call over MCP, the inputs each one accepts, and the API endpoint behind it.
Once you connect an assistant, these tools become available to it. Each one wraps a LeadX API endpoint and accepts the same JSON fields that endpoint accepts, so anything you can filter on over HTTP you can ask for in chat.
Tools are filtered by your account's live entitlements — an assistant only ever sees the tools your account can use.
Available tools
| Tool | What it does | Endpoint |
|---|---|---|
leadx_search_companies | Search and enrich company records | POST /v1/companies |
leadx_search_contacts | Search professional contacts at a company | POST /v1/contacts |
leadx_find_email | Find a business email address | POST /v1/emails/find |
leadx_find_mobile_number | Find a contact's mobile number | POST /v1/mobile-numbers/find |
leadx_get_all_attributes | Aggregate every attribute for one company | POST /v1/all-attributes |
leadx_get_bbb | Better Business Bureau ratings and reviews | POST /v1/bbb |
leadx_get_google_reviews | Google rating, review count, and review text | POST /v1/google-reviews |
leadx_search_ucc_debtors | UCC filings from the debtor's side | POST /v1/ucc/debtor |
leadx_search_ucc_secured_parties | UCC filings from the lender's side | POST /v1/ucc/secured_party |
Company and contact data
leadx_search_companies
Searches company records by domain, name, address, phone, industry, geography, or firmographics. At least one filter is required.
Common inputs are url, company_name, city, state, zip_code, industry, naics_code, number_employees, annual_revenue, and keywords. Use near_zip_code with radius for a distance search, and include_fields to return only the fields you need. Returns up to 50 records per page.
leadx_search_contacts
Finds people at a company. At least one filter is required.
Common inputs are url for the company domain, plus name, title, title_hierarchy, department, city, state, and linkedin_url. Returns up to 50 records per page.
leadx_find_email
Returns one work email address. Supply either first_name, last_name, and url together, or a linkedin_url on its own.
leadx_find_mobile_number
Returns one mobile number from a linkedin_url, or from a first and last name with a company name or website.
Company attributes and reputation
leadx_get_all_attributes
Returns company, contact, UCC, review, BBB, and D&B attributes for a single company in one call. Identify the company with url, phone, or company_id, and pass exclude to drop collections you do not need — contacts, ucc_records, or google_reviews.
leadx_get_bbb
Returns BBB ratings, accreditation status, complaints, and reviews. Identify the business with url, company_name, phone, address, or bbb_url, or search a segment with category, accredited, bbb_rating, or bbb_rating_numerical.
leadx_get_google_reviews
Returns Google rating, review count, review text, and review summaries. Identify the business with url, company_name, phone, google_maps_url, or categories.
UCC filings
Both UCC tools search the same filings from opposite sides, and accept the full filter set documented on their endpoint pages — filing status and dates, collateral text, the structured asset taxonomy, filing classifications, geography, and firmographics.
leadx_search_ucc_debtors
Searches from the debtor's side, where filters like url, company_name, and city describe the business that pledged collateral. Narrow by lender with secured_party_name.
leadx_search_ucc_secured_parties
Searches from the secured party's side, where url and secured_party_name describe the lender. Narrow by borrower with debtor_name.
For equipment finance, LeadX classifies collateral into a structured asset taxonomy covering industry, category, equipment type, and manufacturer. Ask for "filings covering John Deere excavators" and the assistant can target that taxonomy directly instead of searching raw collateral text. The filter names are listed on the UCC endpoint reference.
Costs and limits
Every tool call is a normal LeadX API call against your account: same permissions, same rate limits, and same credit charges as calling the endpoint directly. Paginate deliberately — asking for a specific number of results keeps an assistant from spending credits on records you do not need.