ee-mcp-public
Related Servers
Alternatives to ee-mcp-public
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables read-only access to BuzzerBeater's public API through MCP tools for retrieving team, player, match, market, national team, and other game data.29MIT
- AlicenseBqualityBmaintenanceEnables credential-free, read-only access to selected public market-data routes via 13 typed MCP tools covering asset mapping, metadata, quotes, listings, global metrics, Fear & Greed, Altcoin Season, and CMC index data.13MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying Kiwify sales, subscriptions, products, and affiliates via the official API. Read-only access for viewing data.MIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only verification of public Countervault receipts and SHA-256 hashes via fixed-host public API requests, without account access or credentials.MIT
- AlicenseBqualityBmaintenanceEnables read-only access to public Star Atlas-inspired game data, profile key audits, DAO treasury/proposal/revenue/Ecosystem Fund information, and signed hub updates, listings, and claims through MCP tools, without signing or writing to any chain.22Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables access to public Amazon profit, referral/FBA fee, ACoS, TACoS, and geo-holdout calculators without a key, plus read-only brand profit and incrementality records with an optional brand key.MIT
TDQS
Scored across 43 tools
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.
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.
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.
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.