Add ownership verification for EKS/ECS MCPs for registry #105
+2
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nineonine
approved these changes
Dec 2, 2025
nineonine
approved these changes
Dec 2, 2025
wzxxing
reviewed
Dec 3, 2025
|
|
||
| LLMs are non-deterministic and they make mistakes, we advise you to always thoroughly test and follow the best practices of your organization before using these tools on customer facing accounts. Users of this package are solely responsible for implementing proper security controls and MUST use AWS Identity and Access Management (IAM) to manage access to AWS resources. You are responsible for configuring appropriate IAM policies, roles, and permissions, and any security vulnerabilities resulting from improper IAM configuration are your sole responsibility. By using this package, you acknowledge that you have read and understood this disclaimer and agree to use the package at your own risk. | ||
|
|
||
| <!-- mcp-name: io.github.awslabs/eks-mcp-server --> |
Contributor
There was a problem hiding this comment.
should awslabs or aws be used here?
Author
There was a problem hiding this comment.
Seems it just has to match the name exactly from the server.json, proposed change
Now I think the org there is just related to the owner of the publisher. But I think it should match the value from repository since the Pypi package (ie. mcp-proxy-for-aws) doesn't map to the GitHub in the file
Contributor
There was a problem hiding this comment.
Got it, as long as you are certain about this change, we can give it a go and try.
There was a problem hiding this comment.
Not clear if the io.github.awslabs is the most appropriate or not. Is it a one-way door?
wzxxing
previously approved these changes
Dec 4, 2025
|
|
||
| LLMs are non-deterministic and they make mistakes, we advise you to always thoroughly test and follow the best practices of your organization before using these tools on customer facing accounts. Users of this package are solely responsible for implementing proper security controls and MUST use AWS Identity and Access Management (IAM) to manage access to AWS resources. You are responsible for configuring appropriate IAM policies, roles, and permissions, and any security vulnerabilities resulting from improper IAM configuration are your sole responsibility. By using this package, you acknowledge that you have read and understood this disclaimer and agree to use the package at your own risk. | ||
|
|
||
| <!-- mcp-name: io.github.awslabs/eks-mcp-server --> |
Contributor
There was a problem hiding this comment.
Got it, as long as you are certain about this change, we can give it a go and try.
Signed-off-by: wzxxing <[email protected]>
wzxxing
previously approved these changes
Dec 10, 2025
add new line at the end of the file Signed-off-by: wzxxing <[email protected]>
wzxxing
approved these changes
Dec 10, 2025
matthewgoodman13
approved these changes
Dec 10, 2025
awsjjzhou
approved these changes
Dec 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes
Add verification strings for AWS EKS and AWS ECS MCP servers for the Official MCP Registry. See their documentation for context
User experience
No change. Metadata changes only.
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change? (Y/N)
Please add details about how this change was tested.
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.