Skip to content

Add a status field indicating if a server is deprecated or active (#210) - #2

Merged
gss2002 merged 1 commit into
gss2002:mainfrom
modelcontextprotocol:main
Aug 2, 2025
Merged

gss2002 merged 1 commit into
gss2002:mainfrom
modelcontextprotocol:main

Conversation

@gss2002

@gss2002 gss2002 commented Aug 2, 2025

Copy link
Copy Markdown
Owner

The following PR adds a new server status field to support the status of servers, like deprecated or active

Details:

  • Add status field to server.json schema with 'active' and 'deprecated' values
  • Update OpenAPI spec to include status field in Server responses
  • Add ServerStatus enum and field to Go model structs
  • Update examples to demonstrate status field usage (active and deprecated)

Since this is my first PR there's a good chance I might have missed something so I'll appreciate any feedback to make this and any PRs in the future easier for you to review 😃

Fixes: modelcontextprotocol#181

Motivation and Context

The main goal is to have a way for server authors to notify registry consumers that a server may no longer be maintained and shouldn't be considered for using.

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context


The following PR adds a new server `status` field to support the status
of servers, like deprecated or active

Details:
* Add status field to server.json schema with 'active' and 'deprecated'
values
* Update OpenAPI spec to include status field in Server responses
* Add ServerStatus enum and field to Go model structs
* Update examples to demonstrate status field usage (`active` and
`deprecated`)

Since this is my first PR there's a good chance I might have missed
something so I'll appreciate any feedback to make this and any PRs in
the future easier for you to review 😃

Fixes: #181

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
The main goal is to have a way for server authors to notify registry
consumers that a server may no longer be maintained and shouldn't be
considered for using.

## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

## Breaking Changes
<!-- Will users need to update their code or configurations? -->

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update

## Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [x] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] My code follows the repository's style guidelines
- [ ] New and existing tests pass locally
- [ ] I have added appropriate error handling
- [ ] I have added or updated documentation as needed

## Additional context
<!-- Add any other context, implementation notes, or design decisions
-->

---------

Signed-off-by: Radoslav Dimitrov <[email protected]>
Co-authored-by: Tadas Antanavicius <[email protected]>
@gss2002
gss2002 merged commit 436fd0c into gss2002:main Aug 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Include mechanism for tagging servers as "archived"

2 participants