TargetWise — B2B Prospecting & Enrichment

Name: TargetWise — B2B Prospecting & Enrichment
Author: sens663

作者：sens663版本 1.0.0i★ –i在云端运行

注册名称ai.targetwise/targetwise

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 其他
你需要填写：Authorization

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： Authorization

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

在终端中运行这条命令

claude mcp add --transport http targetwise https://targetwise.ai/api/mcp --header 'Authorization: your-value'

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "targetwise": {
      "url": "https://targetwise.ai/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "targetwise": {
      "type": "http",
      "url": "https://targetwise.ai/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

Authorization 机密必填 HTTP header
Enter Bearer followed by your TargetWise workspace API key from Dashboard → Developers.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过域名 targetwise.ai 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32398 个服务器的 0%
发布到注册中心的时间比此分类中其他 32398 个服务器的 57% 更新
基础检查结果等于或优于此分类中其他 32398 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

TargetWise — B2B Prospecting & Enrichment 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：Authorization

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.0.0）于30天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, AI Deprecations

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

AI Deprecations

作者：aideprecations.com

AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

TargetWise MCP

TargetWise is a B2B data enrichment platform that helps sales, revenue operations and AI teams turn incomplete company and contact records into usable business data. It combines waterfall contact enrichment with company intelligence and delivers results through its web platform, API and MCP connectors.

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, directory manifest and MIT-licensed Claude plugin and Desktop connector 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 plugin

Install the plugin from TargetWise's GitHub marketplace in Claude Code:

/plugin marketplace add sens663/targetwise-mcp

/plugin install targetwise@targetwise

Enter a dedicated TargetWise workspace API key when prompted. The plugin marks the key as sensitive and uses Claude's credential storage. Node.js 20 or newer is required. Local MCP tools work in Claude Code and compatible local Cowork environments; they do not run in Claude web chat. See the plugin README for tools, data handling and validation.

The plugin includes the TargetWise logo and company description. This is TargetWise's own marketplace, not an approved listing in Anthropic's directory. Official directory publication requires a separate submission and review through Anthropic's developer portal.

Claude Desktop and Claude web

Download the TargetWise Claude Desktop extension and follow the Claude setup guide. The package includes the TargetWise logo and company description. Enter a dedicated workspace API key in its sensitive API key setting.

The dependency-free Node.js bridge and manifest are in connectors/claude. It forwards requests only to the fixed TargetWise HTTPS endpoint, refuses redirects and does not read local files or run shell commands. Run node --test tests/claude-connector.test.mjs to check the bridge. Run python3 scripts/package-claude-connector.py from this repository's root to build the bundle.

Claude web accounts with custom request-header support can use the hosted MCP endpoint directly. The setup guide includes the required Authorization header. Directory submission and Anthropic approval are separate from downloading this custom extension.

Claude Code

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:

gemini extensions install https://github.com/sens663/targetwise-mcp

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.

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 Claude plugin and Desktop bridge, 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