Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.smeet666/mcp-lrclib

NPM · MCP-LRCLIB · 2 COMPONENTS · SCANNED SEP 20

Search tracks on LRCLIB and fetch plain or time-synced (LRC) lyrics. No API key.

0 this week 94 Trust /100
Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to smeet666/mcp-lrclib). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 21 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 792 tokens (~264/item across 3 items; 3 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
Install

How do I install the io.github.smeet666/mcp-lrclib server?

io.github.smeet666/mcp-lrclib runs locally as an npm package, launched with npx -y mcp-lrclib. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-lrclib

# add to Claude Code
claude mcp add smeet666-mcp-lrclib -- npx -y mcp-lrclib
// .cursor/mcp.json
{
  "mcpServers": {
    "smeet666-mcp-lrclib": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-lrclib"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "smeet666-mcp-lrclib": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-lrclib"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add smeet666-mcp-lrclib -- npx -y mcp-lrclib
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "smeet666-mcp-lrclib": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-lrclib"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add smeet666-mcp-lrclib --command npx --arg -y --arg mcp-lrclib
# ~/.hermes/config.yaml
mcp_servers:
  smeet666-mcp-lrclib:
    command: "npx"
    args: ["-y", "mcp-lrclib"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "smeet666-mcp-lrclib": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-lrclib"
      ]
    }
  }
}
# add to Vellum
assistant mcp add smeet666-mcp-lrclib -t stdio -c npx -a -y mcp-lrclib
// mcp.json
{
  "mcpServers": {
    "smeet666-mcp-lrclib": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-lrclib"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1
    • Stability: 0.97 → pass security
  • 18 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.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 13 Sept 26 +1
    • Stability: 0.97 → pass security
  • 11 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.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 −3
    • Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/mcp-lrclib@2.0.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo smeet666/mcp-lrclib
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/smeet666/mcp-lrclib/.github/workflows/publish.yml@refs/tags/v2.0.1
Rekor log index 2644827343
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:1921da421314163af82e6de4832e76b53a6252ed176e28126628de481f8dd0c213f4182000fdd7ef8e4c258f04e650e907bc180753e0fb0b6f421db98

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~687 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. 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 →

Tool Tokens
get_lyrics ~346

Fetch the lyrics of one track from LRCLIB, given the id returned by search_tracks, or an exact artist and title. Set 'format' to "synced" for karaoke-style lyrics with a timestamp on every line, "plain" for the text alone, or "both". Check 'has_synced_lyrics' in the search results first: not every track has timed lyrics. Lyrics can be long, so the text is truncated by default: check 'truncated' and call again with 'offset' set to 'next_offset' to continue reading. Instrumental tracks come back with status "instrumental" and no text, which is a valid answer, so do not retry them. Always cite 'attribution' when showing lyrics to a user.

NameTypeReqDescription
album_namestringAlbum name, to pick between releases.
artist_namestringArtist name, matched exactly by LRCLIB. Required when 'id' is absent.
duration_secondsnumberTrack duration, to pick between versions of differing length.
formatstring'plain' returns the text only. 'synced' returns LRC text plus a parsed list of timestamped lines. 'both' returns each of them.
idintegerLRCLIB track id, as returned by search_tracks. Preferred over the name fields.
max_charsintegerMaximum characters of lyrics text to return in this call.
offsetintegerCharacter offset to resume from, for lyrics longer than max_chars.
track_namestringSong title, matched exactly by LRCLIB. Required when 'id' is absent.
NameTypeReqDescription
attributionstringyes
next_offsetyes
notesarrayyes
offsetintegeryes
paginated_formstringyesWhich body the character counts and the offset describe. Timed text carries its timestamps, so it is longer than the words alone.
plain_lyricsstring|nullyes
returned_charsintegeryes
sourcestringyes
statusstringyes
synced_linesyesParsed timestamped lines.
synced_lines_truncatedbooleanyes
synced_lyricsstring|nullyesRaw LRC text, one timestamp per line.
total_charsintegeryes
trackobjectyes
truncatedbooleanyes

No examples provided.

get_track ~95

Look up one LRCLIB track by its id and return its metadata without the lyrics: title, artist, album, duration, and whether plain and time-synced lyrics exist. Use this to confirm you have the right release or version before calling get_lyrics, or to check whether timed lyrics exist for a track id you already hold.

NameTypeReqDescription
idintegeryesLRCLIB track id, as returned by search_tracks.
NameTypeReqDescription
duration_formattedstring|nullyesDuration as m:ss, when known.
notesarrayyes
sourcestringyes
trackobjectyes

No examples provided.

search_tracks ~246

Search LRCLIB for tracks by title, artist or album, and get the id needed to fetch lyrics with get_lyrics. Give either 'query' as free text, or 'track_name' and 'artist_name' separately for a narrower search. Results carry metadata only: title, artist, album, duration, and whether plain and time-synced lyrics exist. Use 'duration_seconds' and 'album_name' in the results to tell releases and re-recordings of the same song apart, and 'has_synced_lyrics' to know whether karaoke-style timed lyrics are available before fetching them. LRCLIB indexes tracks by their metadata, so it cannot search for a word appearing inside the lyrics.

NameTypeReqDescription
album_namestringAlbum name, to narrow a structured search.
artist_namestringArtist name, for a structured search.
limitintegerMaximum tracks to return. LRCLIB returns up to 20 per search.
querystringFree-text search, for example 'nino ferrer le sud'. Use this or the fields below.
track_namestringSong title, for a structured search.
NameTypeReqDescription
notesarrayyes
result_countintegeryes
resultsarrayyes
sourcestringyes
total_availableintegeryesTracks LRCLIB returned before applying 'limit'.

No examples provided.

Common questions

What is the io.github.smeet666/mcp-lrclib server?

io.github.smeet666/mcp-lrclib is listed in the public MCP registry as io.github.smeet666/mcp-lrclib. Search tracks on LRCLIB and fetch plain or time-synced (LRC) lyrics. No API key. This page covers its npm package (mcp-lrclib).

Is the io.github.smeet666/mcp-lrclib server safe to use?

io.github.smeet666/mcp-lrclib scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.smeet666/mcp-lrclib server expose?

io.github.smeet666/mcp-lrclib exposes 3 tools: search_tracks, get_lyrics, get_track. Their descriptions and schemas cost roughly 687 tokens of context every time the server is loaded.

Is the io.github.smeet666/mcp-lrclib server still maintained?

io.github.smeet666/mcp-lrclib 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.smeet666/mcp-lrclib server under?

io.github.smeet666/mcp-lrclib declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.