mcp-dsh-plugins
Related Servers
Alternatives to mcp-dsh-plugins
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceEnables coding agents to search an index of 22k+ MCP servers, agent skills and coding-agent plugins directly from chat, returning matches with stars, install commands and page links, plus trending repos and curated best-of topic lists. Read-only, no API key required, usable via a hosted HTTP endpoint or locally over stdio.4MIT- 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
- 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 gradedqualityCmaintenanceEnables MCP clients to search a catalogue of 648,000+ coding-agent mods with measured metrics such as token cost, security grade, and originality, and to fetch full details for any mod directly from Claude Desktop or any MCP client.10 npmMIT
- AlicenseBqualityDmaintenanceMCP server for accessing Claude Code plugins. Enables retrieving plugin lists and detailed information via MCP clients like Claude Desktop, Cursor.2MIT
- AlicenseNot gradedqualityBmaintenanceProvides aggregated plugin index data from GitHub and npm as an MCP server, enabling search, stats, and sync via natural language or commands.17 npmMIT
TDQS
Scored across 4 tools
search_plugins, get_plugin, and check_runtime each target a clearly different operation (fuzzy search, single-package detail, compatibility check). list_categories partially overlaps with search_plugins since search supports category filtering, but it still adds distinct category enumeration and counts.
All four tools follow a consistent snake_case verb_noun pattern: search_plugins, get_plugin, list_categories, check_runtime. The convention is predictable and readable across the whole set.
Four tools is modest but well-matched to a read-only plugin catalog: discovery, detail, taxonomy, and compatibility. Nothing feels redundant, though the surface is somewhat thin for a marketplace.
The set covers search, single-plugin detail, category listing, and DSH version compatibility, which is most of the read-only lifecycle for a plugin registry. Minor gaps like explicit pagination or listing all plugins (partially covered by search with no query) are workable.