Skip to main content
Glama
dmpeters

good_honker

by dmpeters
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to good_honker

No user-submitted related servers found.

    Related Servers

    • good_wook

      dmpeters
      A
      license
      B
      quality
      B
      maintenance
      A conversational MCP server that provides natural-language access to Phish's show history, setlists, and song statistics via live Phish.net data.
      11
      MIT

    • rs3-mcp

      Buecherfresser
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes RuneScape 3 data from the RuneMetrics, Grand Exchange, and RuneScape Wiki APIs, enabling natural language queries for player profiles, XP gains, quests, item prices, and wiki content.
      -

    • Sessionize

      labjp-mcp
      A
      license
      A
      quality
      C
      maintenance
      MCP server for accessing Sessionize event data. Query speakers, sessions, and schedules from any Sessionize-powered conference using natural language.
      6
      4
      Apache 2.0

    • urmusic-mcp

      ipaud
      A
      license
      A
      quality
      B
      maintenance
      A personal MCP server that analyzes your Spotify streaming history locally, enabling queries, artist insights, and recommendations using a local SQLite database.
      7
      MIT
    • LabelGrid MCP Server by labelgrid

      LabelGrid MCP Serverofficial

      labelgrid
      A
      license
      A
      quality
      A
      maintenance
      The official MCP server for LabelGrid's music distribution platform, enabling natural language management of music catalogs, releases, files, analytics, royalties, webhooks, and distribution via a thin wrapper over the LabelGrid public API.
      84
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the Goose database: shows by date, search, random, song history, stats, jam charts, venues, upcoming, albums, appearances, extras, setlists, and health check. While there are multiple date-related tools, their descriptions clearly differentiate them (calendar day across years vs. specific date vs. most recent).

    Naming Consistency3/5

    All names are snake_case and readable, but there is no consistent verb-noun pattern. Some use verbs (search_shows, get_setlist), others are noun phrases (song_history, venue_info), and a few are adjectives (random_show, latest_show). This mixed style reduces predictability, though not to the point of confusion.

    Tool Count5/5

    With 14 tools, the server covers a rich domain without being bloated. Each tool serves a distinct purpose in the Goose data ecosystem, from search to deep dives into songs, venues, and show extras, making the count well-scoped.

    Completeness5/5

    The surface is thorough for a band-centric server: it includes discovery (search, random, history), detailed song data (history, stats, jam charts), show-specific info (setlist, extras), venue metadata, upcoming shows, album discography, and guest appearances. There are no obvious gaps for the intended use case.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources