Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Find company websites and verified business emails through the Potarix Enricher API.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.potarix.com/mcp在终端中运行这条命令
claude mcp add --transport http potarix https://api.potarix.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"potarix": {
"url": "https://api.potarix.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"potarix": {
"type": "http",
"url": "https://api.potarix.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.potarix.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 Potarix 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.1.2)于5个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Rystic
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Start, seed, clock, inspect and diff Rystic API simulators from your agent.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP wrapper for Potarix Enricher. Lets AI agents resolve company websites, find verified emails, and pull complete company rosters — and (with one human-in-the-loop card capture) sign up and pay for credits entirely from the agent.
| tool | what it does | cost |
|---|---|---|
lookup_company_website | company name → website URL | 2 credits |
find_person_email | named person + company/domain → verified email | 25 credits |
find_decision_maker_email | category + domain → likely buyer name + email | 25 credits |
find_linkedin_email | LinkedIn profile URL → verified email | 10 credits |
find_company_emails | domain → public company contact roster | 25 credits |
find_all | one company name → website + DMs + full company email list | sum of above |
check_balance | credits, email, saved-card status, key count | free |
start_checkout | get a Stripe URL to add a card the first time | n/a |
topup_credits | charge the saved card and add credits | n/a |
1 credit = $0.01. Trial accounts start with 25 free credits. Every endpoint floors at the worst-case provider COGS — a hit never loses money, and short-circuited waterfall calls earn margin.
| transport | endpoint | best for |
|---|---|---|
| Streamable HTTP (hosted) | https://api.potarix.com/mcp | remote agents (Claude, ChatGPT) — no install |
| stdio (npm package) | npx -y potarix-mcp | local/desktop clients |
Both expose the same nine tools. The hosted server is stateless and multi-tenant: every request is authorized by its own Authorization: Bearer ptk_live_... header, so there is no per-user deployment.
Point any MCP client that speaks Streamable HTTP at https://api.potarix.com/mcp and send your key as a bearer token:
{
"mcpServers": { "potarix": { "url": "https://api.potarix.com/mcp", "headers": { "Authorization": "Bearer ptk_live_your_key" } } } }
npm install -g potarix-mcp
Or run it without a global install:
npx -y potarix-mcp
Set your Potarix API key:
export POTARIX_API_KEY=ptk_live_your_key
Optional:
export POTARIX_API=https://api.potarix.com/enricher
{
"mcpServers": { "potarix": { "command": "npx", "args": ["-y", "potarix-mcp"], "env": { "POTARIX_API_KEY": "ptk_live_your_key" } } } }
claude mcp add potarix npx -- -y potarix-mcp
Then add POTARIX_API_KEY to the environment where Claude Code runs.
npm install
npm run build npm run smoke # stdio transport: connect + tools/list
npm run start:http # serves on http://127.0.0.1:8080/mcp (set PORT to change)
POTARIX_MCP_URL=http://127.0.0.1:8080/mcp npm run smoke:http
Environment variables:
| var | default | purpose |
|---|---|---|
POTARIX_API_KEY | — | API key (stdio only; HTTP reads it per-request from the bearer header) |
POTARIX_MCP_TRANSPORT | stdio | http to run the Streamable HTTP server (or pass --http) |
PORT / HOST | 8080 / 127.0.0.1 | HTTP bind address |
POTARIX_MCP_PATH | /mcp | HTTP request path |
POTARIX_MCP_ALLOWED_HOSTS | — | comma-separated host allow-list; enables DNS-rebinding protection |
POTARIX_API | https://api.potarix.com/enricher | API base URL override |
This repo includes server.json for the official MCP Registry. The entry is multi-surface: it declares both the hosted Streamable HTTP remote (https://api.potarix.com/mcp) and the npm stdio package (potarix-mcp), so a single registry record advertises two ways to connect.
The registry validates the npm package by fetching it and checking that its published mcpName matches the server name, so the npm package must be published first, at the same version named in server.json (packages[].version).
Publishing steps (version-bump first, then npm, then registry):
# 1. Bump package.json + server.json to the same new version (e.g. 0.1.3).
npm publish
mcp-publisher login github mcp-publisher publish
The package mcpName in package.json must match server.json:
io.github.Potarix/potarix-mcp