@withpica/mcp-server 2.60.0 → 2.61.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -11,6 +11,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
11
11
 
12
12
  ## [Unreleased]
13
13
 
14
+ ## [2.61.0] - 2026-05-23
15
+
16
+ ### Changed
17
+
18
+ - **`pica_provenance_certificate` is now actually callable.** The tool's description has always been "Generate a provenance certificate", but the underlying SDK call did `GET /admin/works/[id]/certificate`, which 404s on any work without a pre-existing certificate. After bumping `@withpica/mcp-sdk@1.32.0`, the tool's executor POSTs to the same path and generates the certificate row. Closes ops_issues c3e64ee2 (NOT_FOUND, 2 events) and b2dddfee (AUTHENTICATION_ERROR, same caller, pre-OAuth-refresh flake). Description updated to disclose that each call writes a new row.
19
+
20
+ ### Added
21
+
22
+ - **`pica_provenance_certificate_get`** — companion tool for the read path. `tier: "read"`, `risk: "safe"`, fetches an existing certificate row without regenerating. Returns 404 NOT_FOUND if no certificate has been generated yet; callers fall back to `pica_provenance_certificate` in that case. Registered alongside the existing generator in `analytics`, `metadata`, `recovery-hints`, `discovery`, and `public-filter`.
23
+
14
24
  ## [2.60.0] - 2026-05-23
15
25
 
16
26
  Exports release. The four catalog export tools accept per-work scope, the catalog export tool's schema matches what the backend actually validates, and `pica_execute` is forgiving of the three call shapes agents emit in the wild.