good_honker

REMOTE · GOOD-HONKER.MINO-YAKKING.COM · SCANNED AUG 3

Ask Claude about Goose shows: setlists, jams, venues, song history. Live from ElGoose.net.

Available components

remote · good-honker.mino-yakking.com 51

51 51 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security46

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability51

AI-judged instruction clarity (fair).Partial
Tool/resource definitions use about 494 tokens (~35/item across 14 items; 14 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management17

Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage67

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
0% of tool parameters carry a description.Fail

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · good-honker.mino-yakking.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http com-mino-yakking-good-honker https://good-honker.mino-yakking.com/mcp

# ~/.codex/config.toml

[mcp_servers.com-mino-yakking-good-honker]
url = "https://good-honker.mino-yakking.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mino-yakking-good-honker": {
      "type": "remote",
      "url": "https://good-honker.mino-yakking.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-mino-yakking-good-honker --url https://good-honker.mino-yakking.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-mino-yakking-good-honker:
    url: "https://good-honker.mino-yakking.com/mcp"

// mcp.json

{
  "mcpServers": {
    "com-mino-yakking-good-honker": {
      "type": "http",
      "url": "https://good-honker.mino-yakking.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
29 Jul 26 49

First indexed and scored.

Show 4 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://good-honker.mino-yakking.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=mino-yakking.com	CN=WE1,O=Google Trust Services,C=US	22 Jul 2026	20 Oct 2026	ECDSA 256	ECDSA-SHA256	92731c053639ce6a0e8622e61b63cd8f
SANs: mino-yakking.com, good-honker.mino-yakking.com, *.good-honker.mino-yakking.com
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of good-honker.mino-yakking.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
mino-yakking.com.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://good-honker.mino-yakking.com/mcp	Verified	200
http (plaintext)	http://good-honker.mino-yakking.com/mcp	Inconclusive	406

MCP tools — 14 exposed · ~494 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

album_info ~30

Goose discography: list albums, or the tracklist of one album.

Input Output Examples

Name	Type	Req	Description
album	string	—	—

No output schema declared.

No examples provided.

appearances ~34

Guest sit-ins / musician appearances, optionally filtered to one person.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	—
person	string	—	—

No output schema declared.

No examples provided.

get_setlist ~36

Goose setlist for a given date (YYYY-MM-DD).

Input Output Examples

Name	Type	Req	Description
date	string	yes	—
include_related	boolean	—	—

No output schema declared.

No examples provided.

jam_chart ~39

Notable jams from the ElGoose jam charts, optionally filtered to one song.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	—
song	string	—	—

No output schema declared.

No examples provided.

latest_show ~23

The most recent show's setlist.

Input Output Examples

Name	Type	Req	Description
include_related	boolean	—	—

No output schema declared.

No examples provided.

ping ~21

Health check and a manifest of what good_honker can do.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

random_show ~19

A random Goose show, with its full setlist.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_shows ~66

Find shows by year, city, state, and/or venue name.

Input Output Examples

Name	Type	Req	Description
city	string	—	—
include_related	boolean	—	—
limit	integer	—	—
state	string	—	—
venue	string	—	—
year	integer	—	—

No output schema declared.

No examples provided.

show_extras ~33

Poster art, images, and external links attached to a show on a given date.

Input Output Examples

Name	Type	Req	Description
date	string	yes	—

No output schema declared.

No examples provided.

song_history ~42

Every time a song has been played (most recent first).

Input Output Examples

Name	Type	Req	Description
include_related	boolean	—	—
limit	integer	—	—
song	string	yes	—

No output schema declared.

No examples provided.

song_stats ~41

Summary stats for a song: times played, debut, last played, jamchart count.

Input Output Examples

Name	Type	Req	Description
include_related	boolean	—	—
song	string	yes	—

No output schema declared.

No examples provided.

this_day_in_history ~56

Every show played on a given calendar day (month 1-12, day 1-31), across years.

Input Output Examples

Name	Type	Req	Description
day	integer	yes	—
include_related	boolean	—	—
month	integer	yes	—

No output schema declared.

No examples provided.

upcoming_shows ~28

Announced upcoming shows (dates on or after today).

Input Output Examples

Name	Type	Req	Description
include_related	boolean	—	—

No output schema declared.

No examples provided.

venue_info ~26

Venue metadata plus how many times Goose has played there.

Input Output Examples

Name	Type	Req	Description
venue	string	yes	—

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

29 Jul 3 Aug