@kooperativa_team/mcp-server
OfficialRelated Servers
Alternatives to @kooperativa_team/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceGive your AI agent access to 60M+ companies and 300M+ verified contacts. Enrich leads, find work emails, discover tech stacks, and identify buying intent — directly from Claude, Cursor, Windsurf, or any MCP-compatible AI agent.1126 npmMIT

DataForB2B MCP Serverofficial
AlicenseAqualityCmaintenanceAllows searching and enriching companies, people, job postings, and social posts via the DataForB2B API, bringing lead generation and market intelligence into MCP-compatible clients like Cursor and Claude.6MIT- AlicenseAqualityAmaintenanceEnables AI agents to discover and enrich real-time B2B company data, including contact details, ratings, websites, and emails, through MCP-compatible clients.5383 npmMIT
- AlicenseAqualityBmaintenanceEnables searching over 1 million enriched job listings from 20,000+ companies directly from MCP-compatible AI tools. Provides tools for job search, company profiles, and AI-powered similar job recommendations with real-time data updates.453 npm2MIT
- FlicenseNot gradedqualityCmaintenanceEnables B2B lead intelligence through seven tools for company lookup, domain enrichment, person search, email finding, and startup discovery, accessible via MCP for AI agents.-
- AlicenseAqualityBmaintenanceEnables AI agents to perform go-to-market workflows such as company and contact enrichment, CRM querying, and controlled, audited writes to a CRM through MCP tools callable from any MCP client.1MIT
TDQS
Scored across 19 tools
Every tool has a clearly distinct role: account/license checks, health probe, person/company lookup/search/check, relationship and signal queries, and monitor lifecycle. Even similar tools like check_person vs enrich_person are explicitly differentiated as cheap existence check vs full profile fetch.
The shared kooperativa_ prefix and snake_case make the set easy to navigate, and action verbs like search, check, enrich, create, and delete are used consistently. Minor deviations exist where resource-first names are used (person_colleagues, company_current_employees, company_hiring_signals), but they still follow an obvious and predictable pattern.
Nineteen tools is on the heavier side, but the count is justified by the server's breadth: people, companies, signals, account utilities, and webhook monitoring. Each tool maps to a distinct operation and none feel redundant.
The surface covers the core workflow well: check existence, search, enrich single/bulk, and related people/company insights, plus monitor create/list/delete. The only notable gap is the lack of an update_monitor endpoint, but this can be worked around with delete and recreate.