modelcontextprotocol / modelcontextprotocol/typescript-sdk
License metadata clarification for server/core 2.0.0
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.4k
- Forks
- 2.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 4
Description
The inspected @modelcontextprotocol/server@2.0.0 and @modelcontextprotocol/core@2.0.0 packages declare MIT in their manifests, while their included LICENSE describes contribution-dependent MIT/Apache-2.0 coverage.
Could you clarify:
- Which license terms apply to these distributions, and whether the manifest labels need correction?
- Where consumers can find the component-level license mapping and required notices, including any bundled third-party components?
Reference source: cc4b41617ce3601b1290d67216ea0b194a3cd9ac.
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
Read reference commit cc4b41617ce3601b1290d67216ea0b194a3cd9ac, then inspect the @modelcontextprotocol/server@2.0.0 and @modelcontextprotocol/core@2.0.0 package manifests and included LICENSE files. Determine the applicable distribution terms, manifest labels, component-level mapping, and bundled third-party notices. Done means the terms and consumer-facing notice location are clearly documented, with any needed metadata correction identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100