CatMapper MCP
OfficialRelated Servers
Alternatives to CatMapper MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceExposes scattered business REST APIs and read-only databases to AI clients through a single MCP endpoint with unified API-key authentication, service- and operation-level authorization, department-scoped filtering, masking, and audit logging. AI agents discover only the tools and data they are permitted to use, without needing to know endpoint addresses, SQL, or credentials.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to browse products, look up orders, and place orders through MCP tools, with API-key authentication, rate limiting, and idempotent order operations.MIT
- AlicenseAqualityCmaintenanceEnables Claude, ChatGPT and other MCP clients to read an Amiqus ID account—clients, onboarding records and steps, check results, templates, case status counts and webhooks—and, when writes are enabled, create records.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search an organization's data ecosystem, explore table- and column-level lineage, retrieve usage queries, manage metadata such as tags, owners, domains, and terms, and work with knowledge documents through MCP tools.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to list, search, inspect, and recommend publicly available, ready-to-use AI products and interactive experiences through a read-only remote MCP endpoint.MIT

apexapi-mcpofficial
AlicenseAqualityDmaintenanceEnables calling 120+ AI models and reading live web pages (scrape, crawl, structured extract) from any MCP client using one API key.9143 npmMIT
TDQS
Scored across 11 tools
Most tools target clearly distinct resources or actions, such as listing datasets versus searching categories. The main potential confusion is between get_node and get_node_page, which both retrieve node representations but at different levels of detail.
Names consistently use snake_case and mostly follow a predictable verb_noun pattern: list_*, get_*, search_*, and preview_*. Minor deviations are translate as a verb-only name and upload_status as a noun phrase, but the overall convention is readable and stable.
With 11 tools, the surface is well-scoped for a database exploration and data-processing server. Each tool appears to cover a distinct operation rather than bloating the set with redundant variants.
Core read, search, listing, and translation workflows are covered, but there are notable lifecycle gaps. preview_merge does not apply merges, upload_status exists without an upload-initiating tool, and there are no create/update/delete operations for the main data entities.