Lab Registry Server
Related Servers
Alternatives to Lab Registry Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables managing a canonical library of agent skills and MCP servers, syncing them across multiple development harnesses, and adding, importing, or configuring them through MCP tools.15 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to find and evaluate ranked MCP servers, skills, and agents for a task, retrieve detailed entry information and install snippets, and optionally report usage outcomes.MIT
- AlicenseAqualityAmaintenanceEnables MCP hosts to discover, browse, and load Agent Skills from one or many SKILL.md libraries over the Model Context Protocol, with namespaced libraries, search/list/get tools, progressive disclosure, and a digest-verified pull client for syncing skills to disk.71MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover, install, and manage SKILL.md skills from a Git-backed registry via MCP tools for search, install, and list operations.35 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search, retrieve, and read skill files from a registry, exposing each skill as an MCP prompt and resource over HTTP or through a stdio bridge.MIT
- AlicenseNot gradedqualityDmaintenanceDiscovers and manages portable agent capabilities (skills and MCP servers) from configurable collections, providing search, inspection, and local installation via CLI and MCP tools.1MIT
TDQS
Scored across 15 tools
Most tools target distinct operations (list/search/suggest entries vs plugins, compliance, validation, reload), and descriptions explicitly cross-reference when to use alternatives. However, several near-duplicate pairs exist (get_entry vs get_entry_by_id, get_plugin vs get_plugin_install_package, check_compliance vs check_compliance_plugin) that could be misselected despite the guidance.
Every tool follows a consistent snake_case verb_noun or noun pattern (get_* , list_*, check_*, search_*, suggest_*, reload_*, validate_*). No camelCase mixing or vague verbs; the longest names still conform to the same convention.
15 tools sit at the top of the well-scoped range and each maps to a plausible registry operation. A few are convenience wrappers (get_entry_by_id, check_compliance_plugin) that slightly inflate the count, but nothing feels gratuitous.
The surface covers the full lifecycle of a read-only marketplace: discovery (list/search/suggest for both entries and plugins), retrieval (entries, plugins, install packages), compliance checking, changelog, stats, schema validation, and cache reload. No obvious operational gaps remain for the agent's workflows.