modelcontextprotocol / modelcontextprotocol/csharp-sdk
DLLs are not Code Signed
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.5k
- Forks
- 814
- Avg merge
- 9d 19h
- Merged PRs (30d)
- 4
Description
Describe the bug
We are going to use MCP C# SDK in our system, but these DLLs are not code signed, which is a blocking issue to us:
- ModelContextProtocol.AspNetCore.dll
- ModelContextProtocol.Core.dll
- ModelContextProtocol.dll
I'd appreciate dev team can code sign the files so that we can continue using this SDK. Thanks!
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 by reviewing the C# SDK's build and release process to find where ModelContextProtocol.AspNetCore.dll, ModelContextProtocol.Core.dll, and ModelContextProtocol.dll are produced and published. Determine the repository's expected code-signing mechanism and verify the resulting packages expose signed DLLs. Done means all three listed assemblies are code signed in distributed SDK artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100