A
licenseNot graded
qualityC
maintenanceEnables querying Kiwify sales, subscriptions, products, and affiliates via the official API. Read-only access for viewing data.
MIT
ee-mcp-public
Related Servers
Alternatives to ee-mcp-public
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides read-only access to Meta Ads API, enabling campaign management, creative analysis, targeting research, and performance analytics via 39 tools.-
- AlicenseNot gradedqualityCmaintenanceEnables read-only access to Pocket Agent's product information, public persona templates, and app catalog. No authentication required.18 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only access to Product Hunt data, including launches, post details, comments, topic search, and user profiles, through MCP tools over Streamable HTTP.MIT
- AlicenseAqualityAmaintenanceEnables querying and acting on any Acumatica ERP tenant's contract-based REST API through 8 generic tools, covering all entities with read-only by default safety.8MIT
- AlicenseAqualityCmaintenanceProvides read-only access to the Mailchimp Marketing API v3 via 18 tools covering 103 endpoints for audiences, members, campaigns, reports, automations, templates, landing pages, e-commerce, and account administration.18218 npmMIT
TDQS
B3.1/5.0
Scored across 43 tools
Disambiguation2/5
Several tools have near-identical names and purposes, such as getApiKeys/listApiKeys, getProviders/listProviders, and getWebhooks/listWebhookEvents, which only differ by internal API module. With 43 tools, an agent can easily select the wrong variant despite reading descriptions.
Naming Consistency3/5
The set is consistently camelCase with get/list prefixes, but it mixes getX and listX for collection endpoints and creates duplicate-looking names across the email and payment domains. The pattern is readable but not predictable enough to be considered mostly consistent.
Tool Count2/5
43 tools is well above a comfortable MCP surface and many are near-duplicates (getApiKeys/listApiKeys, getProviders/listProviders). The server covers two domains, but the number feels heavy rather than tightly scoped.
Completeness3/5
As a read-only/public surface, it exposes a broad set of list and detail endpoints across email and payment resources. However, several resources are list-only with no detail lookup, and there are no write or management operations, so lifecycle coverage is incomplete for common workflows.