LOLZTEAM MCP
Related Servers
Alternatives to LOLZTEAM MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to search and monitor Dutch and Belgian classifieds (Marktplaats and 2dehands) for listings, seller profiles, and categories.845 PyPI4MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to browse and search NGA forum posts, including browsing forum sections, viewing post details with replies, and searching posts by keyword.-
- FlicenseAqualityDmaintenanceConnects AI assistants to thousands of Tapatalk-enabled forums, enabling browsing, reading, searching, and optional posting.14-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and analyze a Telegram account as a read-only knowledge source, allowing chat discovery, message search, history reading, contact inspection, and media download without exposing any mutating Telegram tools.13Apache 2.0
- AlicenseAqualityDmaintenanceEnables browsing and searching Reddit content through read-only tools that access Reddit's official API. Supports searching posts, retrieving subreddit information, fetching hot posts, and getting detailed post information.54MIT
- AlicenseAqualityCmaintenanceEnables interaction with USCardForum, a Discourse-based community focused on US credit cards and points. Provides 22 tools for discovering topics, reading content, researching user profiles, and managing authenticated actions like notifications and bookmarks.22MIT
TDQS
Scored across 24 tools
The forum_* and market_* families target clearly distinct resources (categories/forums/threads/posts/users/tags vs listings/categories/filters/sellers), and read vs write tools are well separated. The only real overlap is the api_list_endpoints/api_describe_endpoint/api_call_endpoint fallback trio, which can reach the same data as the dedicated tools, though the descriptions explicitly tell the agent to prefer the dedicated ones.
Every tool follows the same domain-prefixed verb_noun pattern: forum_list_threads, forum_get_post, market_get_item, market_list_categories, api_call_endpoint. Deviations (forum_search, market_search) are verb-only but still consistent with the prefix convention, so the pattern is immediately predictable.
24 tools is at the heavy end, but the server legitimately spans two distinct APIs (Forum and Market) plus a generic read-only API fallback, and each tool maps to a concrete resource or filter. Only marginal consolidation (e.g. categories/filters/games helpers) seems possible.
The read-only surface is nearly exhaustive: forum search, hierarchy, threads, posts, comments, users, tags, plus market search, item detail, filters, seller feedback, inventory value and currencies, with api_call_endpoint as a catch-all. Gaps are minor (no write operations by design, and a few market conveniences must be assembled from search/filters).