relic-mcp 0.5.0 → 0.7.0

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
     {
       "name": "relic",
       "description": "Publish a file from your machine as an encrypted, shareable link. The agent encrypts locally, uploads only ciphertext, and hands back a URL whose fragment holds the key, so the service stores something it cannot read.",
-      "version": "0.5.0",
+      "version": "0.7.0",
       "source": "./",
       "author": {
         "name": "The Bushido Collective",
@@ -21,6 +21,6 @@
     }
   ],
   "metadata": {
-    "version": "0.5.0"
+    "version": "0.7.0"
   }
 }

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "relic",
-  "version": "0.5.0",
+  "version": "0.7.0",
   "description": "Publish a file from your machine as an encrypted, shareable link. The agent encrypts locally, uploads only ciphertext, and hands back a URL whose fragment holds the key, so the service stores something it cannot read.",
   "mcpServers": "./mcp-servers.json",
   "author": {

package/README.md

@@ -4,9 +4,7 @@ Publish a file as an encrypted relic and get back a shareable link. The
 encryption key is generated on your machine and is never sent to the service.
 
 ```bash
-claude mcp add relic \
-  --env RELIC_SERVICE_ORIGIN=https://relik.link \
-  -- npx -y relic-mcp@latest
+claude mcp add relic -- npx -y relic-mcp@latest
 ```
 
 Then: *"publish ./report.md as a relic."*
@@ -18,8 +16,7 @@ For any client that takes a JSON config:
   "mcpServers": {
     "relic": {
       "command": "npx",
-      "args": ["-y", "relic-mcp@latest"],
-      "env": { "RELIC_SERVICE_ORIGIN": "https://relik.link" }
+      "args": ["-y", "relic-mcp@latest"]
     }
   }
 }
@@ -33,9 +30,10 @@ For any client that takes a JSON config:
 3. Encrypts locally with AES-128-GCM under RFC 8188 `aes128gcm` framing.
 4. Uploads **only ciphertext**, straight to object storage under a signed URL.
    It does not pass through the Relic service.
-5. Tells the service three things: a coarse renderer class from an eight-value
-   list, this client's name, and the ciphertext's byte length. Not your
-   filename, not the mimetype, not the contents.
+5. Tells the service four things: a coarse renderer class from an eight-value
+   list, this client's name, the ciphertext's byte length, and the title,
+   which defaults to the filename and is stored in the clear. Not the
+   mimetype, not the contents.
 6. Records the relic's id, key, and publish token locally, in a 0600 file
    under your user config directory, so the relic can be republished from
    this machine later. See [Republishing](#republishing). The service never
@@ -68,8 +66,9 @@ existing link sees the new content; there is no new link to hand out.
 ```
 
 It takes `relic_id` (the 26-character id the original publish returned) and
-`path`, plus an optional `filename` override and an optional `ttl_days` that
-is forwarded on the request. Versions count from 1: `relic_publish` reports
+`path`, plus optional `filename` and `title` overrides and an optional
+`ttl_days` that is forwarded on the request. Versions count from 1:
+`relic_publish` reports
 version 1, each republish reports the next number, and the URL never changes
 across them. A relic's lifetime is fixed at its first publish and carries
 across versions.
@@ -151,9 +150,11 @@ binding the tarball to a specific commit and workflow.
 
 | Tool | Input | Notes |
 |---|---|---|
-| `relic_publish` | `path`, optional `filename`, `ttl_days` | A filesystem path. Inline content is deliberately not accepted, so the plaintext never joins the key in your transcript. A relic is kept until it is deleted; `ttl_days` (an integer, 1 to 3650) gives it a lifetime. Reports the relic as version 1. |
+| `relic_publish` | `path`, optional `filename`, `title`, `ttl_days` | A filesystem path. Inline content is deliberately not accepted, so the plaintext never joins the key in your transcript. A relic carries a plaintext title defaulting to the filename and stored by the service in the clear for link previews; pass `""` to publish without one. A relic is kept until it is deleted; `ttl_days` (an integer, 1 to 3650) gives it a lifetime. Reports the relic as version 1. |
 | `relic_lookup_source` | `path` | Reads local state to find whether this machine already published that file, and returns the exact `relic_republish` call. Calls no server. |
-| `relic_republish` | `relic_id`, `path`, optional `filename`, `ttl_days` | Publishes a new version under the same key, so the share URL is unchanged. Works only on the machine holding that relic's key and publish token; a taken-down relic can never be revived. |
+| `relic_list` | optional `limit`, `include_expired`, `verify`, `refresh` | Every relic this machine published, newest first. The only tool that enumerates: lookup answers only from the file a relic came from. A name this machine never recorded is recovered by decrypting the relic's own envelope in one 64 KB range request, or comes back `null` with the reason. A relic the service will not serve is listed with which of removed, expired, exhausted, or unreachable it is. Each row carries the share URL, fragment included, so each row is a credential. Reaching the service spends one of a relic's finite opens; recovered names are cached, so a repeat listing spends none. |
+| `relic_show` | `relic_id`, optional `include_content` | One relic in detail, including how many versions the service holds against how many this machine recorded, and with `include_content` the current decrypted content. Read it before republishing anything you did not just write: republish replaces what the link serves, so without the read-back the edit is blind. Content that is not valid UTF-8 is reported as size and type rather than mangled text. |
+| `relic_republish` | `relic_id`, `path`, optional `filename`, `title`, `ttl_days` | Publishes a new version under the same key, so the share URL is unchanged. Replaces the plaintext title (defaults to the new filename; pass `""` to remove it). Works only on the machine holding that relic's key and publish token; a taken-down relic can never be revived. |
 | `relic_read_comments` | `relic_id` | Returns the relic's comments oldest first, decrypted locally, with the author and a count of any that would not decrypt. Works only on the machine that published. |
 | `relic_comment` | `relic_id`, `body`, optional `display_name` | Leaves a comment, encrypted on this machine, authorized by the publish token and attributed as `publisher`. Body caps at 4096 bytes of UTF-8. |
 | `relic_describe_client` | none | Explains the encryption path. Reads nothing, sends nothing. |
@@ -162,10 +163,11 @@ binding the tarball to a specific commit and workflow.
 
 | Variable | Meaning |
 |---|---|
-| `RELIC_SERVICE_ORIGIN` | The Relic service to publish to. |
+| `RELIC_SERVICE_ORIGIN` | The Relic service to publish to. Unset means the hosted service, `https://relik.link`. Set it to publish to your own. |
 | `RELIC_ORIGIN` | Origin used to build the shareable URL. Defaults to the above. |
 | `RELIC_CLIENT_NAME` | Reported to the service as the publishing client. |
 | `RELIC_PUBLISH_STATE` | Where the publish state file lives. Defaults to `$XDG_CONFIG_HOME/relic-mcp/publish-state.json`, or `~/.config/relic-mcp/publish-state.json`. |
+| `RELIC_METADATA_CACHE` | Where recovered filenames are cached. Defaults to `metadata-cache.json` beside the publish state. Holds no key and no token; deleting it costs one round of recovery. |
 | `RELIC_MCP_HTTP` | `1` to serve Streamable HTTP instead of stdio. |
 | `RELIC_MCP_PORT`, `RELIC_MCP_HOST` | HTTP bind. Defaults to `127.0.0.1:7333`. |
 | `RELIC_MCP_ALLOWED_ORIGINS` | Comma-separated `Origin` allowlist for HTTP. |