mcp-domain-to-linkedin-url-resolver vs exa
mcp-domain-to-linkedin-url-resolver and exa are both search and web MCP servers. exa scores higher (100 vs 85 out of 100). exa has more GitHub stars (5.1k), and exa was updated more recently (4 days ago). The table compares them side by side.
| mcp-domain-to-linkedin-url-resolver | exa | |
|---|---|---|
| Score | 85 / 100 | 100 / 100 |
| What it does | Resolves a company domain or name to its LinkedIn URL from search results, with confidence. | Connect AI agents to Exa for web search, content fetching, and multi-step research. |
| Publisher | Verified: mambabuilt.com | Verified: exa.ai |
| Grades | Maintenance A, Licence A, Quality C | Maintenance A, Licence A, Quality A |
| npm downloads a week | 418 | Not on npm |
| Runs | Local | Remote |
| Works with | Claude Code, Claude Desktop, Cursor, Codex, Gemini CLI, VS Code, Windsurf | Claude Code, Claude Desktop, Cursor, Codex, Gemini CLI, VS Code, Windsurf, ChatGPT |
| GitHub stars | 2 | 5,142 |
| Last commit | 16 Oct 2026 | 19 Oct 2026 |
| Licence | MIT | MIT |
| Listed since | 19 Oct 2026 | 19 Oct 2026 |
| Install mcp-domain-to-linkedin-url-resolver | Install exa |
Questions
Is mcp-domain-to-linkedin-url-resolver or exa more popular?
exa has more GitHub stars: 5,142.
Can I use mcp-domain-to-linkedin-url-resolver and exa together?
Yes. AI assistants can load several MCP servers at once. Install both and the assistant picks the right one for each task.