TargetWise — B2B Prospecting & Enrichment

ai.targetwisev1.0.0更新於 Oct 6, 2026

Find companies and B2B contacts, enrich profiles, and look up work emails and business phones.

已驗證Streamable HTTP可網頁執行Business & Commerce Data & Analytics

概覽

AI 產生的概覽

讓助理尋找公司與 B2B 聯絡人、補充選定的記錄，並查詢可用的工作電子郵件與公司電話。

功能: TargetWise 是託管的 B2B 開發與資料補充 MCP 服務。十一項工具涵蓋公司身分解析、帶篩選條件的公司搜尋、聯絡人與員工搜尋、公司與聯絡人資料補充、工作電子郵件查詢、公司電話查詢以及電子郵件反查。搜尋有上限（每頁 25 個候選、最多 10 頁；公司身分搜尋每頁最多 5 個候選），結果會回傳 matched、partial 或 not_found 狀態，並保留 unresolved_fields。
適用情境: 適合企業客戶研究、在 CRM 驗證前補充營收營運記錄、需要電子郵件或公司電話時的聯絡人補充，以及讓 AI 回覆以結構化的公司與專業人士記錄為依據。它只擷取資料，不發送開發信，也不寫入 CRM。
執行需求: 需要可連上網路的遠端 Streamable HTTP 端點 TargetWise 帳號，以及從 Dashboard → Developers 取得的工作區 API 金鑰，透過 Authorization: Bearer 標頭傳送（README 也建議存入 TARGETWISE_API_KEY 環境變數）。用戶端必須支援自訂 bearer 標頭；僅支援 OAuth 的用戶端無法直接連線。

安裝前請注意

Authorization 標頭帶有工作區 API 金鑰，請勿納入版本控制，應使用密鑰儲存機制。呼叫會依工作區額度計費，搜尋與補充會消耗付費額度，不要自動補充每一個候選記錄。回傳的電話不一定是已驗證的手機號碼，工作電子郵件查詢也不代表信箱歸屬或可送達。欄位可用性因記錄而異，資料來自第三方服務。

安裝

在 SourceWeft 中

開啟儀表板中的 TargetWise — B2B Prospecting & Enrichment，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "targetwise": {
      "type": "http",
      "url": "https://targetwise.ai/api/mcp"
    }
  }
}

README

TargetWise MCP

Company and contact data for AI agents. Connect to TargetWise over Streamable HTTP to find companies and employees, enrich selected records, and retrieve available work emails and business phones.

MCP endpoint: https://targetwise.ai/api/mcp
Documentation: https://targetwise.ai/developers/mcp
Product: https://targetwise.ai/mcp/overview
Official registry name: ai.targetwise/targetwise
Authentication: a TargetWise workspace API key in the Authorization: Bearer ... header

This repository contains the official connection guide, client configurations and directory manifest for the hosted TargetWise service. The hosted server implementation and database are not distributed in this repository.

Start with one useful lookup

Create a TargetWise account at https://targetwise.ai and obtain a workspace API key from Dashboard → Developers.
Store the key in your client's secret store or the TARGETWISE_API_KEY environment variable.
Connect a client that supports Streamable HTTP and custom bearer headers.
Use bounded search, inspect the candidates, then enrich the selected company or professional.

Customer-key clients must use /api/mcp. The hosting platform reserves /mcp; it is not the customer-key endpoint.

Claude Code

claude mcp add --transport http targetwise https://targetwise.ai/api/mcp \  --header "Authorization: Bearer ${TARGETWISE_API_KEY}"

claude mcp add --transport http targetwise https://targetwise.ai/api/mcp \  --header "Authorization: Bearer ${TARGETWISE_API_KEY}"

Alternatively, use the included .mcp.json project configuration. It reads TARGETWISE_API_KEY from the environment. Keep credentials out of version control.

Cursor

In Cursor's MCP settings, configure a remote server with the endpoint and Authorization header. The included cursor.mcp.json uses Cursor's environment interpolation syntax.

Gemini CLI

Install the included extension:

When prompted, enter your TargetWise workspace API key. The extension declares a sensitive setting, TARGETWISE_API_KEY, and uses it in the Bearer header. Gemini CLI stores sensitive extension settings in its system keychain. Calls still consume your TargetWise workspace credits.

Clients that require an OAuth authorization flow cannot connect directly to this bearer-key gateway. Use a client that supports custom authentication headers. Do not interpret directory publication as approval by an AI platform.

Eleven tools

Tool	Purpose
`targetwise_find_companies`	Resolve a company name, website or registration number into candidates
`targetwise_search_companies`	Find companies using supported business, location, industry or technology filters
`targetwise_search_contacts`	Find professional candidates at known company domains
`targetwise_search_employees`	Search employee records by company, person name, job title, department or seniority
`targetwise_get_employee`	Retrieve available details for one selected employee
`targetwise_autocomplete_company`	Populate company fields from an identity lookup
`targetwise_enrich_company`	Retrieve a profile for one selected company or supported identifier
`targetwise_enrich_contact`	Retrieve requested contact fields and available professional profile context
`targetwise_find_work_email`	Look up one known professional's available work email
`targetwise_find_phone`	Look up one known professional's available business phone
`targetwise_reverse_email_lookup`	Resolve one business email into available person and employer context

Discovery definitions are published at https://targetwise.ai/.well-known/mcp/server-card.json. They are generated from the same tool definitions used by the running server.

Registry and discovery

The official MCP Registry record is active at https://registry.modelcontextprotocol.io/v0.1/servers/ai.targetwise%2Ftargetwise/versions/latest. Directory review and client-gallery approval are separate from registry publication.

[AllMCPs listing]

Where it fits

Enterprise account research: identify a company and add business context to a brief.
Revenue operations: enrich selected records before applying your CRM's validation and merge rules.
Contact enrichment: request an email or business phone when that field is needed.
AI product development: ground responses in structured company and professional records.

The host owns decisions and downstream actions. TargetWise MCP does not send outreach or write to a CRM.

Usage and result handling

Data calls are metered against the workspace allowance. Consult https://targetwise.ai/pricing for current plans and result charges. Do not automatically enrich every search candidate.

Company and contact prospecting is bounded to 25 candidates per page and 10 pages; company identity search returns at most five candidates per page.
Field availability varies. Handle matched, partial and not_found outcomes and preserve unresolved_fields.
A returned phone is not necessarily a verified mobile number.
Work-email lookup does not establish mailbox ownership or deliverability.
Optional professional profile fields depend on account access and record availability.
Retrieval timestamps describe when TargetWise made a request; source provenance is included only where available.

Protocol

Use Content-Type: application/json and Accept: application/json, text/event-stream. The documented compatibility flow uses protocol version 2025-11-25: initialize, send notifications/initialized, then list or call tools. Follow the live documentation for additional supported request modes.

The tools retrieve data, but calls can consume credits; consequently their annotations include readOnlyHint: false and idempotentHint: false.

Service and licensing

The MIT license covers the connection examples and documentation in this repository. Access to the hosted service and returned data is governed by TargetWise's plans and terms: https://targetwise.ai/legal/terms. The service and data are not licensed under MIT.

Privacy: https://targetwise.ai/legal/privacy
Security: https://targetwise.ai/trust/security
Support: https://targetwise.ai/company/contact

來源：README.md，提交 b3a1227

工具

工具後設資料尚未被收錄。

版本歷史

v1.0.0最新Oct 6, 2026