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