eksisozluk-mcp
Related Servers
Alternatives to eksisozluk-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables read-only search and retrieval of public İŞKUR job listings, individual job details, the 81 Turkish provinces, and official announcements through MCP tools.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only exploration of community content such as posts, topics, games, comments, user profiles, notifications, discounts, news, and trending items through MCP tools or a CLI.MIT
- AlicenseNot gradedqualityCmaintenanceProvides read-only, unauthenticated access to Turkish financial news, Borsa İstanbul equities and KAP disclosures, TEFAS funds, newspaper front-page archives, and platform status monitors for MCP clients.MIT
- 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
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to scan, search, and read Reddit posts and comments using Reddit's public JSON endpoints, with no API credentials required.34 npmMIT
- 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
TDQS
Scored across 6 tools
Each tool targets a clearly distinct resource or action: channel topic listing, trending topics, title search, full topic entries, daily best (debe), and a health probe. The only mild adjacency is between channel_topics and trending, but their descriptions make the boundary explicit.
All names share the eksisozluk_ prefix and snake_case formatting, so the namespace is predictable. However, several names are bare noun phrases (debe, health, trending, channel_topics) while others use verb_noun (search_topics, get_topic), so the action pattern is not fully uniform.
Six tools is well-scoped for a read-only site browser, comfortably within the 3–15 range. Each tool covers a distinct browsing need and none feels like filler.
The surface covers discovery (trending, channel, search, debe), content retrieval (get_topic), and connectivity (health), which supports the core workflows. Minor gaps remain: no author/user profile browsing and no direct single-entry or random-topic fetch, though agents can work around these via get_topic.