Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/reference/api/official-registry-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,8 @@ Results are ordered by server name, then by version string, both ascending. Vers

To retrieve only the latest version of each matching server, pass `version=latest`. Returned records have `_meta["io.modelcontextprotocol.registry/official"].isLatest` set to `true`. Keep the same filters when following `metadata.nextCursor` to subsequent pages.

Deprecating a version does not, by itself, remove its `isLatest` flag. A deprecated version can remain the latest version of a server, so `version=latest` and the `/versions/latest` endpoint do not guarantee an active result. Clients that display only active servers must also check `_meta["io.modelcontextprotocol.registry/official"].status == "active"`. To select an older active version when the latest is deprecated, inspect the server's version history and apply your own selection policy; filtering the latest result does not select a replacement automatically.

Example: `GET /v0.1/servers?search=filesystem&version=latest`

When the complete server name is known, use `GET /v0.1/servers/{url-encoded-server-name}/versions/latest` (or a specific version) instead of substring search. For example: `GET /v0.1/servers/io.github.example%2Fweather/versions/latest`.
Expand Down
2 changes: 1 addition & 1 deletion docs/reference/api/openapi.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -1064,7 +1064,7 @@ components:
example: "2023-12-01T11:00:00Z"
isLatest:
type: boolean
description: Whether this is the latest version of the server
description: Whether this is the latest version of the server. Deprecation does not, by itself, remove this flag; check status separately to determine whether the version is active.
example: true
additionalProperties: false
additionalProperties: true
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ The `_meta` field in `server.json` is **different** from the `_meta` field retur
- `status`: Server lifecycle status (active, deprecated, deleted)
- `publishedAt`: When the server was first published
- `updatedAt`: When the server was last updated
- `isLatest`: Whether this is the latest version
- `isLatest`: Whether this is the latest version. Deprecation does not, by itself, remove this flag; clients must check `status` separately to determine whether the version is active.

**Example: What you publish (server.json)**

Expand Down
2 changes: 1 addition & 1 deletion pkg/api/v0/types.go
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ type RegistryExtensions struct {
StatusMessage *string `json:"statusMessage,omitempty" doc:"Optional message explaining status change (e.g., deprecation reason, migration guidance)"`
PublishedAt time.Time `json:"publishedAt" format:"date-time" doc:"Timestamp when the server was first published to the registry"`
UpdatedAt time.Time `json:"updatedAt,omitempty" format:"date-time" doc:"Timestamp when the server entry was last updated"`
IsLatest bool `json:"isLatest" doc:"Whether this is the latest version of the server"`
IsLatest bool `json:"isLatest" doc:"Whether this is the latest version of the server. Deprecation does not, by itself, remove this flag; check status separately to determine whether the version is active."`
}

type ResponseMeta struct {
Expand Down
Loading