A
licenseA
qualityA
maintenanceMCP server for the Mamba Labs Bluesky Brand Presence Mapper actor on Apify. Resolve a company domain to its Bluesky account with exact follower, following and post counts.
1
89 npm
MIT
mcp-legal-entity-resolver
by mambalabsdev
Related Servers
Alternatives to mcp-legal-entity-resolver
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs GitHub Organization Signal Scanner actor on Apify. Resolve a company domain to its GitHub organization with repo, language and activity signals.186 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs X Twitter Brand Presence Mapper actor on Apify. Resolve a company domain to its X handle, profile URL and follower metrics.178 npmMIT
- AlicenseAqualityAmaintenanceMCP server that wraps the Apify Workplace Program Detector actor, taking a company domain and returning the employee programs it publishes, such as ERGs, DEI, wellbeing, parental leave, and volunteering.164 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs Trustpilot Reputation Enricher actor on Apify. Resolve a company domain to its Trustpilot rating, review count and claimed status.175 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs People Finder & Email Verifier actor on Apify. Give it a company domain, name or LinkedIn URL and it returns the people at that company who match your role, seniority and department filters, each as a structured contact record with an optional verified business email.165 npmMIT
TDQS
A4.5/5.0
Scored across 1 tool
Disambiguation5/5
There is only one tool, so there is nothing to confuse it with. Its purpose (domain → registered legal entity) is stated unambiguously, including what it does not do (not a company database, not a risk product).
Naming Consistency5/5
A single tool named resolve_legal_entity follows a clear verb_noun snake_case pattern. There is no competing convention to clash with it.
Tool Count3/5
The server is deliberately scoped to one operation, and that operation is substantive (multi-register lookup with audit trail). Still, a single tool is thin for a server surface and forces any multi-domain or reverse-lookup workflow to be handled outside it.
Completeness4/5
The core read path is well covered: resolution, confidence/method metadata, rejected candidates, and multiple registers. Gaps are minor — no batch resolution of many domains and no reverse lookup (name/company number → domain), which an agent would have to loop around.
Maintenance
ActivityActive
ResponsivenessNo issues