LinkedIn URL Resolver vs PayMCP
Side-by-side comparison of two Model Context Protocol servers. Pick the right one for Claude Desktop, Claude Code, or Cursor.
Resolves company domain or name to its LinkedIn URL with confidence scores and firmographic data.
Comparison
| Feature | LinkedIn URL Resolver | PayMCP |
|---|---|---|
| Pricing | Free | Free |
| Installs | — | 2 |
| Rating | — | — |
| Verified | — | |
| Hosted | — | — |
| Tools | — | — |
| Category | development | development |
| Author | mambalabsdev | blustAI |
| Repo | mambalabsdev/mcp-domain-to-linkedin-url-resolver | blustAI/paymcp |
When to pick LinkedIn URL Resolver
Resolves company domain or name to its LinkedIn URL with confidence scores and firmographic data.
When to pick PayMCP
Lightweight payments layer for MCP servers: turn tools into paid endpoints with a two-line decorator. [PyPI](https://pypi.org/project/paymcp/) · [npm](https://www.npmjs.com/package/paymcp) · [TS repo](https://github.com/blustAI/paymcp-ts)
Looking for something else? Browse all MCPs or check trending this week.