Swarmnest
OfficialRelated Servers
Alternatives to Swarmnest
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceTool search engine for AI agents. One API call to discover the best MCP server for any task. 900+ services indexed with 4-dimensional value ranking.MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching and retrieving details of 41,000+ agent skills, MCP servers, Claude Code plugins, and agentic loops from any MCP-capable agent.MIT
- AlicenseAqualityFmaintenanceMCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.54MIT
- 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.-
- AlicenseNot gradedqualityFmaintenanceRemote MCP server enabling agents to search, buy, and publish reusable knowledge via nine agent-native tools without API keys or custodied wallets.MIT
- AlicenseNot gradedqualityDmaintenanceProvides access to over 226 tools and 1,208 skills across web search, image/video generation, SEO, scraping, and more, allowing any MCP-compatible agent to discover, search, and call AI tools via a hosted gateway.36 npm1MIT
TDQS
Scored across 6 tools
Each tool targets a distinct resource-action pair: categories, directory entries, skills, and marketplace products are never confused. The parallel list/search/get structure across the directory and skill catalogs is clear because the descriptions explicitly tie get_entry to search_directory slugs and get_skill to search_skills slugs.
All six names follow a strict snake_case verb_noun convention (list_categories, search_directory, get_entry, search_skills, get_skill, list_marketplace_products). The verb set (list/search/get) is applied predictably to each resource.
Six tools is well-scoped for a catalog-browsing server, with a clean list/search/get grouping per domain. It is slightly thin in that the marketplace domain gets only a single list tool, but nothing is redundant or excessive.
Directory and skill domains have near-complete coverage (enumerate, search, fetch detail), and field-level detail is returned by the get tools. Minor gaps: no way to enumerate skill categories/formats/platforms for use as filters, and no get_product detail tool for marketplace items beyond the list payload.