Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
作者提供的说明(英文原文)
Multi-source entity enrichment: company data, contacts, email verification, and phone validation
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
CLEARBIT_API_KEY, HUNTER_API_KEY, APOLLO_API_KEY, TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, ENRICHMENT_CACHE_TTL标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"enrichment": {
"command": "npx",
"args": [
"-y",
"@intelagent/mcp-enrichment"
],
"env": {
"CLEARBIT_API_KEY": "your-value",
"HUNTER_API_KEY": "your-value",
"APOLLO_API_KEY": "your-value",
"TWILIO_ACCOUNT_SID": "your-value",
"TWILIO_AUTH_TOKEN": "your-value",
"ENRICHMENT_CACHE_TTL": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add enrichment --env CLEARBIT_API_KEY=your-value --env HUNTER_API_KEY=your-value --env APOLLO_API_KEY=your-value --env TWILIO_ACCOUNT_SID=your-value --env TWILIO_AUTH_TOKEN=your-value --env ENRICHMENT_CACHE_TTL=your-value -- npx -y @intelagent/mcp-enrichment运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"enrichment": {
"command": "npx",
"args": [
"-y",
"@intelagent/mcp-enrichment"
],
"env": {
"CLEARBIT_API_KEY": "your-value",
"HUNTER_API_KEY": "your-value",
"APOLLO_API_KEY": "your-value",
"TWILIO_ACCOUNT_SID": "your-value",
"TWILIO_AUTH_TOKEN": "your-value",
"ENRICHMENT_CACHE_TTL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"enrichment": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@intelagent/mcp-enrichment"
],
"env": {
"CLEARBIT_API_KEY": "your-value",
"HUNTER_API_KEY": "your-value",
"APOLLO_API_KEY": "your-value",
"TWILIO_ACCOUNT_SID": "your-value",
"TWILIO_AUTH_TOKEN": "your-value",
"ENRICHMENT_CACHE_TTL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
ENRICHMENT_CACHE_TTL env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 IntelagentStudios 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:CLEARBIT_API_KEY, HUNTER_API_KEY, APOLLO_API_KEY, TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.1)于8个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Vexa, emailmd, MCP WhatsApp Cloud
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP server for multi-source entity enrichment — company data, contact lookup, email verification, phone validation, and email discovery.
Uses Clearbit, Hunter.io, and Twilio APIs. Works in mock mode with no API keys configured.
# Clone and build from source
git clone https://github.com/opafex/opafex-mcps.git cd opafex-mcps npm install && npm run build
Requires Node.js 20+.
Create or edit .mcp.json in your project root:
{
"mcpServers": { "enrichment": { "command": "node", "args": ["/path/to/opafex-mcps/packages/enrichment/dist/index.js"], "env": { "CLEARBIT_API_KEY": "sk-...", "HUNTER_API_KEY": "...", "TWILIO_ACCOUNT_SID": "...", "TWILIO_AUTH_TOKEN": "..." } } } }
Omit the env block to run in mock mode.
enrich_companyEnrich company data from a domain name or company name. Returns industry, employee count, funding, tech stack, social profiles, and more.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | One of domain or companyName | Company website domain (e.g. "stripe.com") |
companyName | string | One of domain or companyName | Company name |
Provider: Clearbit
Example response
{
"success": true, "company": { "name": "Company for stripe.com", "domain": "stripe.com", "description": "A leading technology company specializing in innovative solutions.", "industry": "Technology", "sector": "Software", "employees": 150, "employeesRange": "101-250", "founded": 2015, "location": { "city": "London", "country": "United Kingdom" }, "socialProfiles": { "linkedin": "https://linkedin.com/company/example" }, "techStack": ["React", "Node.js", "PostgreSQL", "AWS"], "type": "private" }, "provider": "mock", "cached": false, "timestamp": "2026-03-15T00:00:00.000Z" }
</details>
enrich_contactEnrich contact/person data from an email address or LinkedIn URL.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | One of email or linkedinUrl | Email address |
linkedinUrl | string | One of email or linkedinUrl | LinkedIn profile URL |
firstName | string | No | First name (optional hint) |
lastName | string | No | Last name (optional hint) |
company | string | No | Company name (optional hint) |
domain | string | No | Company domain (optional hint) |
Provider: Clearbit
verify_emailVerify an email address for deliverability. Returns validity, deliverability score, disposable/free provider detection, role-based detection, and SMTP validation.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | Email address to verify |
Provider: Hunter.io
Example response
{
"success": true, "email": "test@example.com", "valid": true, "deliverable": true, "disposable": false, "freeProvider": false, "role": false, "score": 95, "provider": "mock", "cached": false }
</details>
verify_phoneValidate and look up a phone number. Returns validity, formatted number, line type (mobile/landline/voip), carrier info, and location.
| Parameter | Type | Required | Description |
|---|---|---|---|
phone | string | Yes | Phone number (any format, E.164 preferred) |
countryCode | string | No | Country dialing code without + (e.g. "1" for US, "44" for UK). Defaults to `"44"` (UK). |
Provider: Twilio
find_emailFind the email address for a specific person at a company.
| Parameter | Type | Required | Description |
|---|---|---|---|
firstName | string | Yes | Person's first name |
lastName | string | Yes | Person's last name |
domain | string | Yes | Company domain (e.g. "stripe.com") |
Provider: Hunter.io
Example response
{
"success": true, "email": "jane.smith@stripe.com", "score": 85, "sources": ["LinkedIn", "Company Website"], "provider": "mock", "cached": false }
</details>
server_info (built-in)Returns server metadata: name, version, registered tools, and resources. Added automatically by @opafex/mcp-shared.
| Resource | Description |
|---|---|
enrichment://status | Provider configuration status (which APIs are active, mock mode) |
When no API keys are configured, all tools return realistic mock data. This is great for development and testing — you can build against the MCP without any API accounts.
Mock mode activates automatically:
CLEARBIT_API_KEY, HUNTER_API_KEY, or TWILIO_ACCOUNT_SID are setCLEARBIT_API_KEY, company/contact tools use real data while email/phone tools fall back to mock)Check enrichment://status resource or the server_info tool to see which providers are active.
| Variable | Type | Default | Description |
|---|---|---|---|
CLEARBIT_API_KEY | string | — | Clearbit API key for enrich_company, enrich_contact |
HUNTER_API_KEY | string | — | Hunter.io API key for verify_email, find_email |
TWILIO_ACCOUNT_SID | string | — | Twilio Account SID for verify_phone |
TWILIO_AUTH_TOKEN | string | — | Twilio Auth Token for verify_phone |
APOLLO_API_KEY | string | — | Apollo.io API key (reserved for future use) |
ENRICHMENT_CACHE_TTL | number (seconds) | 86400 (24h) | How long to cache enrichment results |
npm run build # Compile TypeScript
npm run dev # Run with tsx (no build needed) npm test # Run tests npm start # Run compiled server
The enrichment service can be used programmatically (not just as an MCP server):
import { EnrichmentService } from '@opafex/mcp-enrichment/service';
import type { CacheProvider } from '@opafex/mcp-enrichment/service';
const service = new EnrichmentService({ clearbitApiKey: 'sk-...', hunterApiKey: '...', });
const result = await service.enrichCompany({ domain: 'stripe.com' });
The default in-memory cache works out of the box. For Redis, SQLite, or any custom store, implement the CacheProvider interface:
import { EnrichmentService } from '@opafex/mcp-enrichment/service';
import type { CacheProvider } from '@opafex/mcp-enrichment/service';
const redisCache: CacheProvider = { async get(key) { /* ... */ }, async set(key, data, ttlMs) { /* ... */ }, async delete(key) { /* ... */ }, async clear() { /* ... */ }, };
const service = new EnrichmentService({ clearbitApiKey: '...', cache: redisCache, });
Found a bug or have a feature request? Open an issue.
Pull requests welcome — see the main repo for development setup.
MIT — see LICENSE.