mcp-lyricscom 1.4.1 → 2.0.0

package/CHANGELOG.md

@@ -0,0 +1,130 @@
+# Changelog
+
+## 2.0.0
+
+- **This server now needs node 24 or later.** Node 20 reached its end of
+  support on 2026-04-30 and node 22 is no longer what this code is built and
+  typed against. That is what makes this a major version: an install on an
+  older node is refused rather than left to fail somewhere later.
+- **Every refusal of an argument opens with `invalid_input`.** A value outside
+  its bounds, of the wrong type, or outside the set an argument reads used to
+  come back in the validator's own words, with no code to branch on.
+- **A container image is published for each version**, on ghcr, for amd64 and
+  arm64. The readme carries the configuration that runs it.
+- The published package carries its changelog, and the entry point it declares
+  for the package root now publishes its types.
+
+## 1.4.1
+
+- The README carries the same badge row as every server here: npm, CI, the
+  licence, the MCP registry entry, the Glama score, and one-click installs for
+  Cursor and VS Code. Each install link encodes this package. npm serves the
+  README frozen at publish time, so a release is what puts it there.
+
+## 1.4.0
+
+- Refuse an argument no tool declares, instead of reading it and dropping it.
+  Every tool's schema already announced `additionalProperties: false`, but the
+  server accepted an undeclared argument silently, computed the answer on the
+  default for it, and returned that answer as if it had honored what was
+  asked. Now the call is refused under the `invalid_input` code, the message
+  names the argument, and offers the declared name when one is close: passing
+  `limt` to `search_lyrics` gets "did you mean 'limit'?", and passing `art` to
+  `search_songs` gets "did you mean 'artist'?".
+
+## 1.3.0
+
+- Say that an offset landed past the end of the words. An empty body under the
+  word "Complete." reads as a song with nothing on file, which is a different
+  fact from the one that happened.
+- Stop calling the site's own suggestions matches. A loose title search returns
+  what lyrics.com guessed at, and a row whose title is not the one asked for sits
+  among them: announcing the list as songs "matching" the query is how one song's
+  words come to be quoted for another. The wording says who chose them, and a
+  note says how to ask for an exact title instead.
+- Never offer a page the schema refuses. A search that reached the last accepted
+  page advertised the next one, sending a caller into an argument that is turned
+  away.
+- Carry the notes into the text block, and keep published text from producing a
+  line shaped like one.
+
+## 1.2.0
+
+- Ship a `.mcpb` bundle on every release, so the server can be installed by
+  opening a file rather than by having npm and a client configuration. The
+  dependencies are compiled into a single file, which makes the bundle 164 kB
+  and five files instead of 3 MB and two thousand: a bundle is unpacked, not
+  resolved, so a copy of `node_modules` would only be dead weight. The npm build
+  still keeps its dependencies external, and the two builds are separate
+  configurations for that reason.
+- Declare the bundle in `server.json`, with the hash the registry requires
+  computed from the released file at publish time rather than committed as a
+  value that goes stale on every build.
+
+## 1.1.1
+
+Housekeeping, with no change to what any tool returns.
+
+- Declare the tool schemas as objects rather than as the raw shape the SDK now
+  deprecates. The emitted `tools/list` is byte for byte what it was.
+- Add an icon and a `websiteUrl` to `server.json`, so the registry has something
+  to show next to the entry.
+
+## 1.1.0
+
+- Cache a response only once it has been read successfully. The cache stored
+  the raw response before parsing, so a page lyrics.com served but this client could
+  not understand stayed pinned for the cache lifetime and was replayed on every
+  retry: the tool could not recover even after the site was healthy again. It
+  now holds the parsed result, which also keeps the raw payload out of memory.
+
+## 1.0.2
+
+- Claim a pacing slot per request instead of per task. A task runs a whole
+  retry chain, so stamping only its start let the next task follow the chain's
+  last request with no gap, below the interval the configuration promises.
+- Honour `Retry-After` when lyrics.com sends one, in both its seconds and its
+  HTTP-date form, instead of guessing a delay. The wait is spent between
+  attempts rather than after the last one, where nobody would use it.
+- Treat HTTP 403 as a refusal to back off from. It was reported as a plain
+  error, so the client kept its pace in the one situation where slowing down is
+  the remedy.
+- Bound the pacing wait by the interval. A clock stepped backwards, by NTP or a
+  resumed virtual machine, made the next request wait for the size of the step,
+  and the queue is serial so every pending call waited behind it.
+- Enforce the pacing floor and the identifying User-Agent in the client rather
+  than only when reading the environment. The client is published through the
+  `./client` export and accepts a caller-built config, so both promises were
+  previously optional for anyone importing the library.
+
+## 1.0.1
+
+- Refresh the packaged README, which now carries one-click install links for
+  Cursor and VS Code and a link to the entry in the official MCP registry.
+- Keep LICENSE to the plain MIT text. License detectors match the file against
+  the canonical template, so the trailing scope note made the package read as
+  unlicensed; that note lives in the README.
+
+## 1.0.0
+
+First stable release. The tool contracts are now considered settled: tool names,
+their parameters and the shape of their structured output will only change in a
+future major version.
+
+Every tool has been exercised end to end against the live site, including the
+paths that are easy to get wrong: pagination continuity in `get_lyrics`, pages
+that carry no lyrics, rejection of non-lyrics.com URLs, and rate limiting
+surfacing as an explicit error.
+
+## 0.1.1
+
+- Enforce a floor on the request interval. `LYRICSCOM_MIN_INTERVAL_MS` is now
+  refused below 500 ms; a lower value falls back to the default 1100 ms and warns
+  on stderr. The pacing that keeps this client polite towards lyrics.com no
+  longer depends on every installation configuring it correctly.
+
+## 0.1.0
+
+Initial release. Three tools over stdio, no API key: `search_lyrics` (word or
+phrase inside the lyrics), `search_songs` (by title), `get_lyrics` (full text by
+id or URL).

package/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2026 smeet666
+Copyright (c) 2026 Damien Bouissou
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/README.md

@@ -5,8 +5,10 @@
 [![license](https://img.shields.io/npm/l/mcp-lyricscom.svg)](./LICENSE)
 [![MCP Registry](https://img.shields.io/badge/MCP_Registry-listed-6E56CF)](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.smeet666/mcp-lyricscom)
 [![Glama](https://glama.ai/mcp/servers/smeet666/mcp-lyricscom/badges/score.svg)](https://glama.ai/mcp/servers/smeet666/mcp-lyricscom)
+[![M8ven](https://m8ven.ai/badge/mcp/smeet666-mcp-lyricscom-pptp4t?variant=verified)](https://m8ven.ai/mcp/smeet666-mcp-lyricscom-pptp4t)
 [![Install in Cursor](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=lyricscom&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIm1jcC1seXJpY3Njb20iXX0%3D)
 [![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat&logo=visualstudiocode&logoColor=white)](https://insiders.vscode.dev/redirect/mcp/install?name=lyricscom&config=%7B%22name%22%3A%22lyricscom%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22mcp-lyricscom%22%5D%7D)
+<!-- m8ven-verify: 3c4d434dcafaac3c25dc86631fb1393b -->
 
 An [MCP](https://modelcontextprotocol.io) server for [lyrics.com](https://www.lyrics.com).
 Search songs by a word in their lyrics, by title, and read the full text.
@@ -42,6 +44,23 @@ claude mcp add lyricscom -- npx -y mcp-lyricscom
 }
 ```
 
+### With Docker
+
+```json
+{
+  "mcpServers": {
+    "lyricscom": {
+      "command": "docker",
+      "args": ["run", "-i", "--rm", "ghcr.io/smeet666/mcp-lyricscom:2.0.0"]
+    }
+  }
+}
+```
+
+`-i` keeps stdin open, which is where the protocol travels, and no `-t` is
+passed: a TTY rewrites the stream and breaks it. The container needs outbound
+HTTPS to `www.lyrics.com`, and nothing else: no volume, no port, no environment variable, no credential.
+
 That is the whole setup. There is nothing to sign up for.
 
 **Bundle, without npm**
@@ -112,6 +131,24 @@ Every variable is optional. Set them in the `env` block of your MCP client confi
 }
 ```
 
+### Avec Docker
+
+```json
+{
+  "mcpServers": {
+    "lyricscom": {
+      "command": "docker",
+      "args": ["run", "-i", "--rm", "ghcr.io/smeet666/mcp-lyricscom:2.0.0"]
+    }
+  }
+}
+```
+
+`-i` garde l'entrée standard ouverte, qui est le canal du protocole, et aucun
+`-t` n'est passé : un terminal réécrit le flux et le casse. Le conteneur a besoin
+d'un accès HTTPS sortant vers `www.lyrics.com`, et de rien d'autre :
+aucun volume, aucun port, aucune variable d'environnement, aucun identifiant.
+
 ### About the User-Agent
 
 This server identifies itself honestly by default, naming the project and linking