Domain Intel MCP vs Vexa
A side-by-side look at the Domain Intel MCP and Vexa MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Domain Intel MCP for communication work over a hosted endpoint; choose Vexa for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Domain Intel MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
domain_report, domain_intel, dns_lookup.
Choose Vexa when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
API_KEY, API_BASE, TRANSCRIBE_ENABLED, RUNTIME_BACKEND.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 69/100 · Great | 62/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | No auth required | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | API_KEYAPI_BASETRANSCRIBE_ENABLEDRUNTIME_BACKEND |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 2,907 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Domain Intel MCP | View Vexa |
Tools & capabilities
Domain Intel MCP tools 6
domain_reportOne-call full dossier on a domain: registration (RDAP), DNS records, email deliverability, and website tech stack, combined into a single report. Use for fast lead qualification, company research, or recon without four separate calls.domain_intelRegistration intelligence for a domain via RDAP (the modern WHOIS). Returns registrar, creation/expiration/last-changed dates, domain age in years, EPP status codes, nameservers, DNSSEC state, and abuse contact. Use to vet a company, assess a lead, or judge how established a domain is.dns_lookupLook up DNS records for a domain via Cloudflare DNS-over-HTTPS. Returns A, AAAA, MX, NS, TXT, CNAME, and SOA records. Use to see where a domain is hosted, who runs its mail and DNS, and what verification/policy TXT records it publishes.email_deliverabilityAssess whether a domain (or the domain of an email address) can receive mail and how strong its sender authentication is. Returns MX presence, SPF and DMARC policy, whether it's a free consumer provider (gmail, etc.) or a known disposable/temp-mail provider, and an overall verdict. Use to qualify leads and flag throwaway signups.tech_stackFingerprint the technology behind a website by fetching its homepage. Detects web server, CMS/framework (WordPress, Shopify, Next.js, etc.), CDN, analytics, and returns the page title, final URL after redirects, and key response headers. Use for competitive research and lead enrichment.subdomainsDiscover a domain's public subdomains (app., api., staging., and so on) from Certificate Transparency logs, querying crt.sh and Cert Spotter in parallel and returning whichever answers first. Useful for mapping a company's public attack surface or infrastructure. If both sources are down the call returns an error rather than an empty list.
Vexa tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Domain Intel MCP
{
"mcpServers": {
"domain-intel-mcp": {
"url": "https://domain.datakoot.com/mcp"
}
}
}
Vexa
{
"mcpServers": {
"vexa": {
"url": "https://api.cloud.vexa.ai/bots"
}
}
}
Frequently asked questions
Domain Intel MCP is categorized under Communication and uses a remote HTTP/SSE transport. Vexa belongs to Communication and uses a remote HTTP/SSE transport. Pick Domain Intel MCP for communication work and Vexa for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Domain Intel MCP has no declared pricing — check the project's own site. Auth: no auth required. Vexa has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add domain-intel-mcp and vexa as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Domain Intel MCP has a quality signal of 69/100 (Great) with 2 views, 0 installs and 1 GitHub stars. Vexa has 62/100 (Good) with 2 views, 0 installs and 2,907 GitHub stars.