modelcontextprotocol / modelcontextprotocol/registry
Prevent valueHint from being submitted with NamedArguments
Open
Nobody has claimed this yet.
v1
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
See: https://github.com/modelcontextprotocol/registry/pull/570/files#r2427093900
There is nothing preventing someone from publishing a server.json with this mistake. Should we validate it at the schema or API level?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked pull request discussion and inspect how server.json submissions are validated at the schema and API levels. Determine where the NamedArguments/valueHint combination should be rejected, then verify that publishing a server.json containing this mistake is refused.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100