MCP OI-Wiki
Related Servers
Alternatives to MCP OI-Wiki
No user-submitted related servers found.
Related Servers
- FlicenseBqualityCmaintenanceProvides 23 modular tools for competitive programming, including problem analysis, algorithm planning, code generation, verification, testing, code review, and learning assistance.23-
- AlicenseNot gradedqualityAmaintenanceFour-layer hybrid search and knowledge graph for AI coding assistants: BM25 + vector embeddings + RAPTOR directory summaries + graph expansion fused into a single MCP tool.276 npm20Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to index and search codebases using semantic search powered by multiple embedding providers (OpenAI, VoyageAI, Gemini, Ollama) and vector database storage.-
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to enhance their responses with relevant documentation through a semantic vector search, offering tools for managing and processing documentation efficiently.9 npm64MIT
- AlicenseNot gradedqualityAmaintenanceA semantic code retrieval engine for AI agents that enables hybrid search, graph expansion, and token-aware context packing, integrating with MCP to provide precise code context to LLMs.9 npm296MIT
- FlicenseNot gradedqualityDmaintenanceA smart code retrieval tool based on Model Context Protocol that provides efficient and accurate code repository search capabilities for large language models.33-
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clearly defined and distinct purpose: searching the OI Wiki for programming competition knowledge.
The single tool name 'search' follows a simple, clear verb pattern. Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions to evaluate.
A single tool is too few for a server that appears to cover a broad domain like a programming competition knowledge base. The scope suggests needs for browsing, filtering, or accessing specific content beyond just search, making the toolset feel thin and underdeveloped.
The tool surface is severely incomplete for the domain. While search is useful, there are obvious gaps such as listing topics, getting detailed articles, or navigating categories, which limits an agent's ability to fully interact with the wiki's content.