ListPlus
ai.listplus/listplusVersion 1.4.2Check and clean B2B contacts in your lists, find leads, size markets, fill work e-mail and mobile.
Status
Responds109 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:30 UTC
- Latency
- 109 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://listplus.ai/mcpResponds109 msNo sign-in
Claude Code
claude mcp add --transport http listplus https://listplus.ai/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: listplus
Remote MCP server URL: https://listplus.ai/mcpCursor
{
"mcpServers": {
"listplus": {
"url": "https://listplus.ai/mcp"
}
}
}VS Code
code --add-mcp '{"name":"listplus","type":"http","url":"https://listplus.ai/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
26 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
add_columnFREE (key, Set up) to set up — Use when a list needs a new column: a score, a label, a lookup, a formula or an AI column. plain, select, formula, rule-based score / label, lookup, in_list and job_change columns cost nothing (Edit on the list). A hubspot column asks the workspace's HubSpot and is PAID: 1 credit per request of up to 100 different values, for the first run and for records that come later. AI criteria in a score and ai_text columns are PAID: 0.02 credits per AI answer (unique values once), Full on the list; their first run costs at most the list's records × that and counts on this connection's day budget, later records run under the list's own day limit. Tell your user the price before you add a paid column. Up to 10 columns per call; call describe_setup first for the fields a rule may use. | No | No | Not declared | Yes |
add_recordsFREE (key) — Use when your user wants records kept in a ListPlus list. add records (JSON objects, column names or common field names) to a list shared with you for editing. A record the list already has (same e-mail, LinkedIn, name + company) is filled in, not doubled. Up to 1,000 per call; the answer names each new record's id and url and what was rejected. | No | No | Not declared | Yes |
check_listFREE (key) — Use when your user asks about the data quality of a ListPlus list. run the 100+ data-quality checks on a list shared with you (or on some of its records): a score, the findings per check with the affected record ids and a proposed fix each (fix_list applies one). | No | Yes | Not declared | Yes |
check_recordsFREE (up to 25 records without a key, 1000 with one) — Use when your user has contact or company records (a CSV, a CRM export, pasted rows) and wants to know what is wrong with them. check contact records for errors with 100+ checks: typos in e-mail domains, role mailboxes (office@), duplicates and near-duplicates, phone codes that do not fit the country, LinkedIn status text in names, placeholders … Returns findings per record with proposed fixes. Nothing is stored or changed. | No | Yes | Not declared | Yes |
copy_recordsFREE (key) — Use to copy or move records between two ListPlus lists. copy records from one list shared with you into another (same kind: contacts or companies) — with `move: true` they are then hidden in the source (restorable, never deleted). A record the target already has is filled in, not doubled; a copy never goes back into a list it came through. Up to 1,000 per call. | Yes | No | Not declared | Yes |
count_companiesFREE — Use when your user asks how big a market is or how many companies fit a description. how many companies match (market size), e.g. { filters: { countries: ["IT"], naics: ["315"] } }; with `by` (needs a key) broken down by one dimension (countries, states, industries, naics, employees, revenue …). Exact values from search_options (for: companies). Loading the companies into a list is load_companies (priced in `options`). | No | Yes | Not declared | Yes |
create_listFREE (key, Set up) — Use when your user wants a new list in their workspace. a new list in the workspace (contacts or companies), with the standard columns or the content types you name, and optional statuses. It is this agent's own list: shared in Full. Then add_column, create_trigger, add_records. | No | No | Not declared | Yes |
create_triggerFREE (key, Set up) to set up — Use when something should happen by itself whenever a record arrives, changes or meets a condition. a rule (trigger) of a list: when a record is new / changed / meets the conditions, set a status (a new name is created), add a tag, hide it (it leaves the normal flow: no checks, rules, enrichment or sync — restorable), hand it to an EXISTING pipeline (pipelines are made by a person in the app), or ENRICH it — PAID per hit, at most budget_per_record credits per record, on THIS connection's day budget (an empty day makes the rule wait, never overspend). Active at once unless activate: false — set an enrich rule up paused until your user agreed to the budget. include_existing runs it once for the records already in the list. Status, tag and hide need Edit on the list; a pipeline the pipeline's share; enrich Full. Call describe_setup first for the fields and operators. | No | No | Not declared | Yes |
derive_columnPAID (needs a key) — Use when a column should be filled by AI from other columns (the gender from the first name, a seniority from the job title). AI tokens by use (usually cents; at most 10 credits per call, within the key's day budget): fill an existing column from others by an instruction (e.g. the gender from the first name, a seniority from the job title, a country from the city). Unique values are asked once. | No | No | Not declared | Yes |
describe_listFREE (key) — Use first whenever your user refers to one of their ListPlus lists: it names the lists you may work on and what you may do there. without list_id: the lists shared with you (name, kind, rows, what you may do). With list_id: its columns (content types, allowed values, which you may write), statuses, the sublists you are limited to, the pipelines you may hand records to, the filter conditions, and the tools this list allows. Call it before working on a list. | No | Yes | Not declared | Yes |
describe_setupFREE (key, Set up) — Use before you build or change a list's columns or rules. what you need before you set something up. Without list_id: whether this connection may set up, the column kinds and the limits. With list_id: the list's columns (kinds), statuses, rules (triggers), the fields a condition may use with their operators, the pipelines you may hand records to, and the HubSpot accounts. Call it before add_column or create_trigger. | No | Yes | Not declared | Yes |
enrich_recordsPAID (needs a key) — Use when records miss a work e-mail, a mobile number, a job title, a LinkedIn profile or company data. per record from a name + company: work e-mail ≈2.39, at most 9 credits; mobile ≈3.84, at most 12; job title ≈1.41, at most 13.5. Charged per hit for e-mail and phone. Use estimate:true first for the exact price of YOUR records (free, no key). Fills fields of contact records (work e-mail, mobile, job title, LinkedIn profile, company, domain, industry, size, place). Send records for a direct result without creating a list, or list_id and record_ids to update shared rows in place. Waits up to 25 s and returns a job_id to poll (get_job) for longer lookups. | No | No | Not declared | Yes |
find_personFREE with a key (rate-limited) — Use when your user names a person, or a role at a company, and wants to know who that is: title, company, LinkedIn profile. find a person: name, job title, company, location, LinkedIn profile, how sure. Give first_name + last_name + company (or domain), a LinkedIn URL, a work e-mail, or a question in `query` ("CFO of Tink in Berlin"). No e-mail or phone in the answer — those are enrich_records. | No | Yes | Not declared | Yes |
fix_listFREE (key) — Use after check_list, once your user agreed to apply fixes, clean values or merge duplicates. apply ONE of: a check's proposed fixes (`check_id` from check_list), cleaning values (trim, casing, placeholders — `clean_values: true`), or merging duplicates (`dedup_key`: email, name_company, linkedin, phone, name — merged rows are hidden, not deleted). Needs editing on the list. | Yes | No | Not declared | Yes |
get_jobFREE (key) — Use after enrich_records answered with a job_id, to fetch the result. the state of an enrich_records job; when it ended, the records with the fields we found (in the order you sent them). | No | Yes | Not declared | Yes |
load_companiesPAID (needs a key) — Use when your user wants the companies of a market as a list, after count_companies sized it. 0.25 credits per company delivered (25 companies = 6.25 credits): the companies a count_companies question found, into a company list in ListPlus — name, domain, website, industry, size, place, LinkedIn page. 10, 25, 50 per call (`limit`), a cursor for the next ones. The same page within an hour costs nothing again. estimate:true shows the price (free, no key). | No | No | Not declared | Yes |
mark_recordsFREE (key) — Use to qualify, tag or put aside records of a ListPlus list (status, tags, hide). set a status (one of the list's, "" clears it — may start the list's rules, as in the app), add or remove tags, or hide records (restorable; hide: false shows them again) in a list shared with you for editing. Nothing is deleted. | Yes | No | Not declared | Yes |
query_recordsFREE (key) — Use to read, filter or count the records of a ListPlus list. read records of a list shared with you: `mode` rows (default; columns you may see, each with id and url), count, or ids (up to 10,000, to pass on as record_ids). Filter by column values or conditions (describe_list names them). | No | Yes | Not declared | Yes |
remove_columnFREE (key, Set up, Full on the list) — Use when a column should go from a list. remove a column from a list (by name or title). Records are never deleted; ask your user before you remove a column a person made. | Yes | No | Not declared | Yes |
search_optionsFREE — Use before search_people, count_companies or load_companies, to get the exact filter values. the filters search_people, count_companies and load_companies accept, and the exact values they take (seniorities, departments, company size, industries, countries, states, NAICS codes, revenue …). Without arguments: the categories; with `category`: its values; with `query`: look a word up ("saas", "apparel"). Copy values exactly. | No | Yes | Not declared | Yes |
search_peoplePAID (needs a key) — Use when your user wants new leads: people by role, seniority, industry, place or company. 2 credits per page of up to 25 people, only for pages the database counts (a repeat within 30 days and an empty result cost nothing). Finds people in the B2B contact database by job title, seniority, department, place, industry, company size or company. The people go into a list in ListPlus (name, job title, company, domain, LinkedIn, place — no e-mail or phone: those are enrich_records, priced in `options`). Up to 4 pages per call, a cursor for the next ones (20 pages deep). Exact values from search_options; estimate:true shows the filters as understood and the price (free, no key). | No | No | Not declared | Yes |
send_to_pipelineFREE (key) to hand over — Use when records should go to the CRM, a sequencer or Slack through one of the workspace's pipelines. records of a list shared with you go to one of the workspace's pipelines you may use (describe_list names them: HubSpot, Slack, lemlist …). The pipeline's data check and release apply: a manual one waits for a person; one that sends by itself delivers at once and is PAID per record delivered — describe_list names each pipeline's `credits_per_record`; it counts on this key's day budget. Tell your user records × that price first. Up to 500 per call. | No | No | Not declared | Yes |
update_recordsFREE (key) — Use when values in a ListPlus list should change. change cells of a list shared with you for editing: per record (`records: [{ id, column: value }]`) or one change for many (`record_ids` or `filter` + `set`). Only the columns you may write (describe_list); `only_empty` fills empty cells only. | Yes | No | Not declared | Yes |
update_triggerFREE (key, Set up) — Use to pause, change or remove a rule of a list. pause, activate, change or remove (remove: true) a rule of a list. Your own rules with the rights of their actions; a rule a person or another connection set up only with the list shared in Full — ask your user first. `actions` replaces the rule's actions (an enrich action named again keeps its settings' place; one left out goes). Enrichment only on your own rules. | Yes | No | Not declared | Yes |
verify_emailPAID (needs a key) — Use when your user wants to know whether e-mail addresses can receive mail before writing to them. 0.3 credits per address (an address checked in the last 7 days costs nothing), so a call costs at most its addresses × that — a fixed price, no estimate: is the e-mail address deliverable (valid, invalid, catch_all, unknown)? Up to 25 addresses per call, answered at once. | No | No | Not declared | Yes |
what_can_you_doFREE — Use first when you are unsure what ListPlus offers, what something costs or how much budget is left. what ListPlus can do for you: every action, the fields we can fill with their price per record, the free limits, and (with a key) your balance and day budget. With `guide`: one chapter of the manual instead (prices, search, lists, setup, rules, limits, examples). | No | Yes | Not declared | Yes |
Details
- Registry status
- Active
- Published
- Nov 11, 2026
- Updated
- Nov 11, 2026
- Categories (suggested)
- CRMSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared