dots-mcp
Related Servers
Alternatives to dots-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables searching and retrieving details of 41,000+ agent skills, MCP servers, Claude Code plugins, and agentic loops from any MCP-capable agent.MIT
- AlicenseAqualityDmaintenanceMCP server for interfacing with the official Model Context Protocol registry. Enables Claude and other MCP clients to dynamically discover, browse, search, and manage MCP servers directly from GitHub.52MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.-
- FlicenseAqualityDmaintenanceEnables searching documentation from GitHub repositories and web pages via MCP tools, with in-memory indexing and caching for fast retrieval.3-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables users to search and discover over 500 AI agent endpoints and x402 APIs directly from MCP-compatible clients like Claude and Cursor. It provides tools to query endpoints by keyword, category, or capability while offering access to detailed provider statistics.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to semantically search GitHub repository documentation by automatically fetching, vectorizing, and indexing content into an Upstash Vector database. It provides a standard MCP interface for agents to retrieve relevant documentation snippets through natural language queries.-
TDQS
Scored across 2 tools
list_dots_resources and search_dots_resources both retrieve from the same dataset, but the list vs. keyword-search split is a clear, conventional distinction. An agent can easily choose the right tool based on whether it wants to enumerate/filter by section or query by keyword.
Both names use consistent snake_case with a verb_noun pattern (list_dots_resources, search_dots_resources) and share the same noun phrase. There is no deviation or mixed convention.
Two tools is on the thin side for a resource-access server; while both are warranted, the surface feels minimal. A third tool (e.g., get resource details) could round it out, but the current count is not unreasonable for a narrow, read-only list.
The domain is a curated resource list about OpenAI Dots; listing (with optional section filter) and keyword search cover the primary retrieval needs. However, there is no explicit operation to fetch a single resource by ID or to list available sections, leaving minor gaps an agent may need to work around.