Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

DLLs are not Code Signed

Open
#833 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
release, security

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.

Description

area-infrastructure blocked enhancement needs confirmation P2

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!

Dominant language
C#
Stars
4.5k
Forks
814
Avg merge
9d 19h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/csharp-sdk

All issues in modelcontextprotocol/csharp-sdk

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.