AgentBase MCP Server
Related Servers
Alternatives to AgentBase MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceSearch 60,000+ AI agent skills from ClawHub, LobeHub, Dify, and GitHub via MCP SSE or REST API. Free, no API key required.4MIT
- 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
- AlicenseBqualityDmaintenanceEnables AI agents to interact with the Clawslist marketplace to browse, create, and manage listings using the Model Context Protocol. It provides a comprehensive set of tools for agent registration, messaging, and offer management directly within MCP-compatible clients.1913 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to search a directory of 13,870+ MCP servers, 4,384+ agent skills, and plugins from Remote OpenClaw, returning install commands directly.351 npm6MIT
- AlicenseNot gradedqualityDmaintenanceEnables access to agent instruction files and prompts for AI development workflows. Provides tools to retrieve and list development rules, security checks, and common prompts from an agents library through MCP protocol.3Apache 2.0
- AlicenseAqualityFmaintenanceAgent-first skill marketplace MCP server. AI agents discover, install, and share skills across 7 platforms via MCP protocol. 15 tools including skill search, download, upload, and agent discovery.184MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: get_featured retrieves high-quality files, get_instruction fetches a specific file by slug, list_categories shows available categories, and search_registry performs keyword searches. The descriptions reinforce these unique roles, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (get_featured, get_instruction, list_categories, search_registry) using snake_case throughout. This predictability enhances readability and usability, with no deviations in style or convention.
With 4 tools, the server is well-scoped for its purpose of accessing an instruction registry. Each tool serves a distinct function (browsing, fetching, categorizing, searching), and there are no redundant or missing tools that would suggest over- or under-engineering.
The tool set provides complete coverage for interacting with an instruction registry: it supports discovery (list_categories, search_registry), retrieval (get_instruction), and quality filtering (get_featured). No obvious gaps exist, as agents can navigate from browsing to accessing specific instructions seamlessly.