Sanitized, fully synthetic server.json A/B pairs for the target-drift signal discussed in
modelcontextprotocol/registry#1706.
No real publishers, no token-bearing URLs, no real tool arguments — registry-schema-shaped only.
Each case directory holds:
a.server.json— the earlier version (bypublishedAt). Absent in the UNKNOWN case.b.server.json— the current version.expected.json— thetargetDriftsignal the Registry should emit (server.json-derivable only), and the action a client must take.
A registry reference diff and a client gate (e.g. the matched-pair suite in peach420fuzz/objekts-production-desk) should consume the same pairs; mismatches become reproducible cases.
The registry signal is necessary, not sufficient. It is a cheap shared hint that lets a client skip
re-diffing history. It never replaces the client re-pinning against its own exact target and its live
tools/list. A false from the registry must never suppress client re-consent, and a missing signal is
UNKNOWN, never "unchanged."
| # | Case | Registry sees | Client action | Point |
|---|---|---|---|---|
| 01 | query-key-set-change | remotesChanged: true |
re-consent | Registry can report query keys (not values) safely. |
| 02 | query-value-rotation | remotesChanged: false |
re-consent | Same key, new value. Registry sees nothing; pinned target still changed. The invariant case. |
| 03 | same-scope-package-rename | packageOwnersChanged: false (+ identifier change) |
re-consent | Owner scope unchanged, installed identity changed. |
| 04 | non-semver-ordering | remotesChanged: true |
re-consent | "Previous" resolved by publishedAt, not the text version sort. |
| 05 | tools-only-drift | all false |
re-consent | Target byte-identical; tool contract changed — only the client (via tools/list) can see it. |
| 06 | unknown-no-baseline | UNKNOWN (absent) |
ask | No parseable prior version. Absent ≠ unchanged; never auto-pass. |
| 07 | version-ordering-record | remotesChanged: true (by publishedAt) |
re-consent | A 3-version history where a naive version-string sort picks the wrong current+previous and silently passes, while publishedAt ordering catches the real origin change. |
Case 05's drift lives only in tools/list, so the pair ships client-side arrays alongside the server.json:
05-tools-only-drift/a.tools.json/b.tools.json— theresult.toolsarrays a client observes (A = baseline, B = current).05-tools-only-drift/tools.expected.json— the tool delta a client must act on:send_emailadded (write/destructive) andread_doc'sreadOnlyHintflippedtrue → falseunder the same name andinputSchema. The registry cannot see any of it.
07-version-ordering-record/versions.json— a syntheticGET /servers/{name}/versionsrecord for one server, listed in descending version-string order on purpose to bait a text/semver-sort consumer. Current is the latestpublishedAt, not the highest version string.07-version-ordering-record/expected.json— correct resolution bypublishedAt(remotesChanged: true) vs the naive version-desc trap (remotesChanged: false, a dangerous silent pass). The divergence is the test.
comparedTo.previousPublishedandcomparedTo.firstare resolved bypublishedAt(GET /servers/{id}/versionsis ordered by publication date;publishedAtis a first-class field), not by the text version sort the list endpoint uses.- Remote URLs compare origin, port, path, and query keys — never query values.
- Packages compare owner scope (
packageOwnersChanged) and identifier; a newversionunder the same identifier is a routine version change, not a target change.