A
licenseA
qualityA
maintenanceResolves company domains to their LinkedIn pages, providing exact follower counts and public firmographics such as industry, company size band, headquarters, founded year, and specialties.
1
382 npm
MIT
mcp-domain-to-linkedin-url-resolver
by mambalabsdev
Related Servers
Alternatives to mcp-domain-to-linkedin-url-resolver
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnriches domains into full company profiles with firmographics and buying signals.-
- AlicenseNot gradedqualityCmaintenanceDomain -> company intelligence for AI agents. Look up company name, country, contacts, and social profiles from any MCP-compatible client.6MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to extract structured firmographic data from public LinkedIn company URLs, returning fields like name, industry, size, and headquarters.-
- AlicenseAqualityAmaintenanceResolves any combination of company name, domain, or LinkedIn URL into the canonical company identity (name, domain, LinkedIn URL) with confidence scores and match method.166 npmMIT
- AlicenseAqualityAmaintenanceEnables agents to enrich domains into public business contact data, including MX/disposable-validated role emails, phones, social profiles, company names, and addresses, while respecting robots.txt; also normalizes URLs and emails into unique domains locally.3MIT
TDQS
A4.6/5.0
Scored across 1 tool
Disambiguation5/5
There is only one tool, so there is no possibility of confusing it with a sibling tool. Its purpose (domain/name to LinkedIn company URL) is stated explicitly, including what it does not do (find people).
Naming Consistency5/5
The single name resolve_linkedin_url follows a clear snake_case verb_noun convention. There are no competing conventions to clash with.
Tool Count4/5
One tool is thin in absolute terms, but the server's scope is intentionally narrow and the tool absorbs single/batch input, firmographics, caching, and multi-platform social output. It is slightly under-scoped rather than mismatched, since there is no second operation (e.g. reverse lookup, cache management) exposed.
Completeness4/5
For a domain-to-LinkedIn-URL resolver, the surface covers the core operation plus batch input, optional firmographics, confidence scoring, and error/run-ID reporting. Minor gaps exist (no reverse LinkedIn-to-domain lookup, no cache inspection/clearing), but nothing that blocks the primary workflow.
Maintenance
ActivityMaintained
ResponsivenessResponsive