io.github.ytkoka/king-crimson-mcp
PYPI · KING-CRIMSON-MCP · SCANNED SEP 20
King Crimson discography and live-performance history with a curated line-up-era model.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 39 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2046 tokens (~170/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.ytkoka/king-crimson-mcp server?
io.github.ytkoka/king-crimson-mcp runs locally as a PyPI package, launched with uvx king-crimson-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · king-crimson-mcp
claude mcp add ytkoka-king-crimson-mcp -- uvx king-crimson-mcp
{
"mcpServers": {
"ytkoka-king-crimson-mcp": {
"command": "uvx",
"args": [
"king-crimson-mcp"
]
}
}
} {
"servers": {
"ytkoka-king-crimson-mcp": {
"command": "uvx",
"args": [
"king-crimson-mcp"
]
}
}
} codex mcp add ytkoka-king-crimson-mcp -- uvx king-crimson-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ytkoka-king-crimson-mcp": {
"type": "local",
"command": [
"uvx",
"king-crimson-mcp"
],
"enabled": true
}
}
} openclaw mcp add ytkoka-king-crimson-mcp --command uvx --arg king-crimson-mcp
mcp_servers:
ytkoka-king-crimson-mcp:
command: "uvx"
args: ["king-crimson-mcp"] {
"McpServers": {
"ytkoka-king-crimson-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"king-crimson-mcp"
]
}
}
} assistant mcp add ytkoka-king-crimson-mcp -t stdio -c uvx -a king-crimson-mcp
{
"mcpServers": {
"ytkoka-king-crimson-mcp": {
"command": "uvx",
"args": [
"king-crimson-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.77 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 11 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed pypi/king-crimson-mcp@0.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_artwork ~71
Get cover art for a release group from the Cover Art Archive. Args: mbid: MusicBrainz release-group ID (from ``search_release``). Returns: A dict with an ``images`` list of {front, back, thumbnails, url}.
| Name | Type | Req | Description |
|---|---|---|---|
| mbid | string | yes | – |
No output schema declared.
No examples provided.
get_credits ~158
Get performer and production credits for an album (release group). Returns the headline artist credit and release-group relationships, plus per-track performer credits resolved from the recording level in MusicBrainz (individual musicians and their instruments), and a deduplicated album roster. Args: mbid: MusicBrainz release-group ID (from ``search_release``). release_mbid: Optional specific release (edition) to read track credits from. If omitted, a representative official release is chosen. Returns: A dict with title, artist_credit, release_used, performers (roster), tracks (per-track credits), relations, and external_links.
| Name | Type | Req | Description |
|---|---|---|---|
| mbid | string | yes | – |
| release_mbid | – | – | – |
No output schema declared.
No examples provided.
get_editions ~196
List physical editions/pressings of an album via Discogs. Resolves the Discogs *master* for the album -- preferring the ``discogs`` relation stored on the MusicBrainz release group (exact match), and falling back to a Discogs title/artist search when no such relation exists. Then lists the master's versions (pressings, reissues, box sets) with format, country, year and community stats. Requires DISCOGS_TOKEN. Args: mbid: MusicBrainz release-group ID (from ``search_release``). max_versions: Max editions to return (1-50). Returns: A dict with master info and a ``versions`` list. ``match_method`` reports how the master was resolved ("musicbrainz-relation" or "discogs-search").
| Name | Type | Req | Description |
|---|---|---|---|
| max_versions | integer | – | – |
| mbid | string | yes | – |
No output schema declared.
No examples provided.
get_incarnations ~103
List King Crimson's line-up eras (incarnations): id, name, date range, members with instruments, key releases, and a one-line note. Use this to look up who played in a given era. Song analysis (song_performance_history) reports per-era counts under `by_incarnation` keyed by the same ids/names, so this is the reference for those. Returns: A dict with an ``incarnations`` list.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_live_history ~155
Search live performance history / setlists via setlist.fm. Useful for King Crimson given their extensive touring: cross-reference official live albums against what was actually played on a given tour. Requires SETLISTFM_API_KEY. Args: query: Optional venue or city keyword to narrow the search. artist: Artist name. Defaults to "King Crimson". year: Optional year filter. limit: Max setlists to return (1-20; one API page). Returns: A dict with a ``setlists`` list of {date, venue, city, country, songs}.
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | – | – |
| limit | integer | – | – |
| query | string | – | – |
| year | – | – | – |
No output schema declared.
No examples provided.
refresh_box_sets_cache ~134
Fetch King Crimson's compilations and box sets from Discogs and cache their tracklists, so song_box_sets can list which box sets contain a song. Filters the artist's Discogs releases to Main-role compilations/box sets (format contains "Comp" or "Box"), which excludes single-show live downloads (those are covered by song_live_releases). Requires DISCOGS_TOKEN. Returns: A summary: releases scanned, box sets cached, and the cache path.
| Name | Type | Req | Description |
|---|---|---|---|
| artist_mbid | string | – | – |
| discogs_artist_id | integer | – | – |
| force | boolean | – | – |
No output schema declared.
No examples provided.
refresh_live_releases_cache ~219
Fetch King Crimson's official live releases from MusicBrainz and cache them locally, parsing a recording date out of each title where possible. Used by song_live_releases to map songs to the live albums that captured them. King Crimson's live catalog is fixed, so this rarely needs re-running. Requires MCP_CONTACT (MusicBrainz User-Agent policy). Args: artist_mbid: MusicBrainz artist MBID. Defaults to King Crimson. max_pages: Safety cap on pages to fetch (100 release groups/page). max_retries: Retries per page on transient error (e.g. MusicBrainz's intermittent 503s) before giving up. force: Re-fetch even if a cache file already exists. Returns: A summary: totals, how many titles yielded a full recording date, and the cache path.
| Name | Type | Req | Description |
|---|---|---|---|
| artist_mbid | string | – | – |
| force | boolean | – | – |
| max_pages | integer | – | – |
| max_retries | integer | – | – |
No output schema declared.
No examples provided.
refresh_setlist_cache ~234
Fetch an artist's complete concert history from setlist.fm and cache it locally as JSON, so song/tour analysis runs instantly and offline. Robust against setlist.fm's intermittent failures: each page is retried with backoff, and any page that still fails is recorded rather than aborting the whole run. King Crimson's history is fixed (band ended 2021), so this rarely needs re-running. Requires SETLISTFM_API_KEY. Args: artist_mbid: MusicBrainz artist MBID. Defaults to King Crimson. max_pages: Safety cap on pages to fetch (20 shows/page). max_retries: Retries per page on transient error before recording it failed. force: Re-fetch even if a cache file already exists. Returns: A summary dict (not the setlists themselves): counts, coverage, any failed pages, date range, and the cache file path.
| Name | Type | Req | Description |
|---|---|---|---|
| artist_mbid | string | – | – |
| force | boolean | – | – |
| max_pages | integer | – | – |
| max_retries | integer | – | – |
No output schema declared.
No examples provided.
search_release ~166
Search MusicBrainz for release groups (albums) matching a query. A "release group" is the canonical album, independent of its many physical editions -- the right granularity for browsing a discography. Use the returned ``mbid`` with the other tools. Args: query: Free-text album title or keywords (e.g. "Red", "Larks' Tongues"). artist: Restrict to this artist. Defaults to "King Crimson". limit: Max results (1-25). Returns: A dict with a ``results`` list of {mbid, title, primary_type, first_release_date, disambiguation}.
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
song_box_sets ~184
List King Crimson box sets / compilations that contain a given song (from Discogs). Complements song_live_releases: that tool maps single-show live albums to eras; this one covers the multi-show box sets and comps that date-matching can't resolve. Run refresh_box_sets_cache first. Args: song: Song title (e.g. "Red"). artist_mbid: MusicBrainz artist MBID (cache key). Defaults to King Crimson. match: "exact" (case-insensitive full track title) or "contains". Returns: The box sets/compilations whose tracklist includes the song, with title, year, format, Discogs URL, and how many times the song appears on each.
| Name | Type | Req | Description |
|---|---|---|---|
| artist_mbid | string | – | – |
| match | string | – | – |
| song | string | yes | – |
No output schema declared.
No examples provided.
song_live_releases ~247
Find official live releases that captured a given song, grouped by incarnation (line-up era). How it works: the song's performance dates come from the setlist cache; live releases carry a recording date parsed from their title. Where a release's recording date matches a date the song was played, that release is taken to contain the song. This is authoritative for single-show live albums; excerpt compilations are an edge case. Requires both caches: run refresh_setlist_cache and refresh_live_releases_cache first. Args: song: Song title (e.g. "Red"). artist_mbid: MusicBrainz artist MBID. Defaults to King Crimson. match: "exact" (case-insensitive full title) or "contains" (substring). Returns: by_incarnation groupings of matched live releases, plus a coverage note stating how many live releases could not be matched by date (box sets, compilations, undated titles) so the caller can decide to search further.
| Name | Type | Req | Description |
|---|---|---|---|
| artist_mbid | string | – | – |
| match | string | – | – |
| song | string | yes | – |
No output schema declared.
No examples provided.
song_performance_history ~179
Trace how often and when a song was played live, from the local setlist cache. Run refresh_setlist_cache first. Aggregates by year and by tour so a song's life across decades and line-ups is visible at a glance. Args: song: Song title to trace (e.g. "Starless", "21st Century Schizoid Man"). artist_mbid: MusicBrainz artist MBID. Defaults to King Crimson. match: "exact" (case-insensitive full title) or "contains" (substring). Returns: A dict with cache_info, performance_count, first/last performance, by_year and by_tour breakdowns, and the list of performances.
| Name | Type | Req | Description |
|---|---|---|---|
| artist_mbid | string | – | – |
| match | string | – | – |
| song | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.ytkoka/king-crimson-mcp server?
io.github.ytkoka/king-crimson-mcp is listed in the public MCP registry as io.github.ytkoka/king-crimson-mcp. King Crimson discography and live-performance history with a curated line-up-era model. This page covers its PyPI package (king-crimson-mcp).
Is the io.github.ytkoka/king-crimson-mcp server safe to use?
io.github.ytkoka/king-crimson-mcp scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.ytkoka/king-crimson-mcp server expose?
io.github.ytkoka/king-crimson-mcp exposes 12 tools: search_release, get_credits, get_editions, get_artwork, get_live_history, and 7 more. Their descriptions and schemas cost roughly 2,046 tokens of context every time the server is loaded.
Is the io.github.ytkoka/king-crimson-mcp server still maintained?
io.github.ytkoka/king-crimson-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.ytkoka/king-crimson-mcp server under?
io.github.ytkoka/king-crimson-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.