infobel-api-mcp
OfficialRelated Servers
Alternatives to infobel-api-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server wrapping the Explee B2B data API, enabling AI agents to search companies and people, enrich contact data, run AI agents, and manage deduplication lists.2-
- FlicenseAqualityDmaintenanceAn MCP server that gives AI agents access to US business entity data, enabling searches across 9 state registries, SEC EDGAR filings, federal contracts, and lobbying disclosures.61-
- AlicenseNot gradedqualityDmaintenanceMCP server giving AI agents real-time web search, page scraping, company intelligence, email discovery, local lead generation, and a persistent knowledge graph. Pay only for what you use, no subscriptions.12 npmMIT

whetstone-mcpofficial
AlicenseAqualityDmaintenanceAn MCP server for U.S. public-records data, enabling AI agents to search business registrations, screen names against government watchlists, and pull federal awards.427 npmMIT- AlicenseAqualityDmaintenanceMCP server for Yelp integration, enabling AI agents to search for local businesses, read reviews, view photos, check hours, find deals, and discover trending spots.1244 npmMIT
- AlicenseBqualityDmaintenanceMCP server for the Japan National Tax Agency Corporate Number API, enabling corporate number lookup and search via local AI clients.31MIT
TDQS
Scored across 28 tools
Most tools map to distinct actions: search, pagination, record retrieval, category lookup, and reference data. The four search_categories_* variants and search_locations vs. get_cities/get_provinces/get_regions are the only areas of minor overlap, but their names and descriptions make the differences clear.
Tool names follow a consistent and predictable pattern: search_ for query operations, get_ for lookups and reference data, all in lower_snake_case. Even similar tools like search_categories_infobel and search_categories_local follow the same naming schema.
At 28 tools, the surface is heavier than ideal, but most of the extra tools are small get_* enumeration endpoints that support the single powerful search_businesses tool. The count is justifiable for a broad business database API, though it feels slightly bloated.
The read-only business search domain is covered well: search with extensive filters, pagination, search status, full and partial record retrieval, category and location lookups, plus reference code lists. There are no obvious workflow gaps or dead ends.