TargetWise Model Context Protocol server
Give your AI host a precise sequence for filtered B2B discovery, candidate selection and field-level enrichment. TargetWise returns structured records; your application chooses the next action.
Start with a free account-status check. The introductory allowance includes 20 email and 5 business-phone results; other operations require confirmed workspace access.
Connection is not entitlement
Check targetwise_account_status first. Paid email and phone pricing does not automatically enable prospecting, company profiles or reverse-email lookup.
| Decision | What to verify |
|---|---|
| Workspace-key host | Streamable HTTP at https://targetwise.ai/api/mcp with an Authorization: Bearer header. Keep the key in credential storage, never chat or a URL. |
| Free status check | Use empty arguments with targetwise_account_status. Inspect free allowance, paid balance, monthly budget and operation access before retrieval. |
| Paid data access | Email and business-phone results are supported. Contact/employee-detail calls must request supported fields without include_profile: true. |
| Evaluation and commercial access | Company, search, reverse-email and extended-profile operations need confirmed access. operation_pricing_unavailable is not fixed by adding balance. |
| Separate approval | Tool discovery does not authorize spending, exports, CRM updates or outreach. Set a host-side tool allowlist and call limit. |
Product behavior checked 15 October 2026 against the current gateway, account-status schema and pricing rules. This page explains selection; the MCP reference owns exact protocol setup.
Choose a job, not unlimited agent access
Choose the smallest useful operation and decide what the host should do when evidence is missing. This is an illustrative planner, not a live lookup or measured result. It accepts no credentials, sends no requests and stores no inputs.
targetwise_find_work_emailA LinkedIn URL, or first and last name with exactly one company domain or company name.
Email-result allowance or supported paid access; check work_email readiness first.
A returned email is not a deliverability check. Review identity before use.
Inspect this operation’s schema →{
"name": "targetwise_find_work_email",
"arguments": {
"first_name": "Alex",
"last_name": "Reed",
"company_domain": "example.com"
}
}Replace example values only in your authenticated host. Complete the protocol setup in the MCP reference first.
Review identity and the requested field before using the result. A match is not permission to send a message or overwrite CRM data.
Enrichment states are shown here. Search instead returns a prospecting_result with candidates and pagination; it is not a matched enrichment result.
targetwise_find_work_emailA LinkedIn URL, or first and last name with exactly one company domain or company name.
Access: Email-result allowance or supported paid access; check work_email readiness first.
Inputs and response schema →targetwise_find_phoneThe same supported person identifiers as work-email lookup; do not mix identifier patterns.
Access: Phone-result allowance or supported paid access; check business_phone readiness first.
Inputs and response schema →targetwise_enrich_companyOne supported identifier: website, company ID, LinkedIn company URL or legal identifier. Legal lookups require country; US legal lookups also require state.
Access: Evaluation allowance and commercial access must be confirmed. Paid production pricing is not currently enabled for this operation.
Inputs and response schema →targetwise_search_contacts1–20 company domains, with optional seniority and location filters. Limit each page to 1–25 candidates; at most 10 pages.
Access: Evaluation allowance and commercial access must be confirmed. Discovery is metered; it is not included merely because tools/list succeeds.
Inputs and response schema →targetwise_reverse_email_lookupA business email; set include_phone and include_profile explicitly to avoid unnecessary disclosure.
Access: Evaluation allowance and commercial access must be confirmed. Paid production pricing is not currently enabled for this operation.
Inputs and response schema →Use the selected operation only after reviewing access. This prompt is a planning aid; your host must enforce permissions and limits.
First use targetwise_account_status. Confirm this workspace can run targetwise_find_work_email with the required inputs and remaining budget. If allowed, make at most one data call using a business record I am permitted to query. Do not request extra fields, search more pages, write to CRM or send messages. Show the returned status and unresolved fields. Stop on unavailable access or missing evidence.
MCP, applied to B2B data
TargetWise gives an AI host six discovery and detail tools, five selective enrichment or lookup tools, and a free account-status check.
The agent starts with an allowlisted company filter or known company domains, inspects a page of up to 25 candidates and selects a relevant entity. Email and phone stay out of contact search results.
A second tool call retrieves only the chosen record or field. The host remains responsible for permissions, call limits and whether returned data can change another system.
The TargetWise tool surface
Shared REST and MCP schemas make invocation and result handling explicit. Advertised capabilities are not a promise of paid-plan access.
Search one page of up to 25 results using supported firmographic, geography, industry, technology or turnover filters.
Search by company domains, seniority and location without revealing contact fields.
Use an opaque ID, website, LinkedIn page or supported legal identifier.
Use LinkedIn or a person name with company context and explicit field switches.
Dedicated tools minimize disclosure; generic phone data is labeled type unknown.
Retrieve available person, role and employer context without claiming mailbox verification.
Agent interaction
The protocol calls and the business decision stay visibly distinct.
Connect your client using its setup guide. Run the free account-status tool before requesting any business data.
Apply required filters or domains, plus explicit page and candidate limits.
Inspect candidate identity and keep the selected opaque ID exactly as returned.
Call one enrichment or field tool, then require separate approval for writes or messages.
Grounding contract
Search tools return prospecting_result with data and pagination. Enrichment tools return matched, partial or not_found with explicit unresolved_fields.
retrieved_at records when TargetWise made the request, not guaranteed source freshness. Company provenance appears only when the selected retrieval route returns it.
1Inside — company/contact search with 25 results per page
2Inside — selective enrichment and lookup
3Outside — CSV, async batch and mass export
4Outside — outreach and CRM writes
Where the tools fit
Use record retrieval inside a larger workflow without granting uncontrolled database access.
Return a small filtered candidate set, choose the relevant account and then retrieve its firmographic context.
Search company domains and request a work email or business phone only for a chosen professional.
Resolve identity and employer context before deterministic routing logic runs.
Use workspace evaluation credits across candidate selection, strong matches, difficult records and no-match cases.
Frequently asked questions
TargetWise MCP combines paginated prospecting with selective retrieval and no autonomous action surface.
Workspace MCP access
Start with a free status check, then evaluate returned fields and no-match behavior on records you are permitted to query. A raw signup or connected host is not successful activation.