A
licenseC
qualityC
maintenanceAn MCP server for querying and analyzing a Stash instance with advanced filters, caching, and personalized recommendations.
7
12
Apache 2.0
mcp-stashbox
by smeet666
Related Servers
Alternatives to mcp-stashbox
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceMCP server for Stash that provides tools, resources, and prompts to query, analyze, and manage a Stash instance, with advanced filtering, caching, and personalized recommendations.7Apache 2.0
- AlicenseAqualityBmaintenanceThis MCP server provides tools to search for songs, artists, and random records from the Bide & Musique catalogue. It offers read-only access to tens of thousands of French songs with no authentication needed.546 npmMIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for querying the MusicBrainz database, providing tools to search for artists, releases, recordings, and browse music metadata.4MIT
- AlicenseBqualityDmaintenanceAn MCP server for obtaining the README content, metadata and search function of CPAN packages.31Apache 2.0
- FlicenseNot gradedqualityCmaintenanceA remote MCP server for the Arxpot processing core, enabling music search, metadata retrieval, and download management with remote storage delivery.-
TDQS
A4.2/5.0
Scored across 10 tools
Disambiguation5/5
Each tool targets a distinct entity (scene, performer, studio, tag) and a distinct action (search vs get), plus find_by_fingerprint and get_sources serve unique purposes. No overlap between tools; clear separation prevents misselection.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: search_<entity> for searching, get_<entity> for retrieval, plus get_sources and find_by_fingerprint. The pattern is uniform across all tools.
Tool Count5/5
10 tools is well-scoped for a read-only search and retrieval server covering four entity types, metadata sourcing, and fingerprint lookup. Each tool earns its place without bloat.
Completeness5/5
The server provides search and retrieval for all core entities (scene, performer, studio, tag), metadata via get_sources, and a fingerprint lookup. For a read-only catalogue interface, the surface is complete with no obvious gaps.
Maintenance
ActivityActive
ResponsivenessUnresponsive