Fix README

Author: halter73

src/ModelContextProtocol.AspNetCore/HttpMcpSession.cs

@@ -12,15 +12,15 @@ public HttpMcpSession(SseResponseStreamTransport transport, ClaimsPrincipal user
     }
 
     public SseResponseStreamTransport Transport { get; }
-    public (string ClaimType, string ClaimValue)? UserIdClaim { get; }
+    public (string ClaimType, string ClaimValue, string Issuer)? UserIdClaim { get; }
 
     public bool HasSameUserId(ClaimsPrincipal user)
         => UserIdClaim?.ClaimValue == GetUserIdClaim(user)?.ClaimValue;
 
     // SignalR only checks for ClaimTypes.NameIdentifier in HttpConnectionDispatcher, but AspNetCore.Antiforgery checks that plus the sub and UPN claims.
     // However, we short-circuit unlike antiforgery since we expect to call this to verify MCP messages a lot more frequently than
     // verifying antiforgery tokens from <form> posts.
-    private static (string ClaimType, string ClaimValue)? GetUserIdClaim(ClaimsPrincipal user)
+    private static (string ClaimType, string ClaimValue, string Issuer)? GetUserIdClaim(ClaimsPrincipal user)
     {
         if (user?.Identity?.IsAuthenticated != true)
         {
@@ -31,7 +31,7 @@ private static (string ClaimType, string ClaimValue)? GetUserIdClaim(ClaimsPrinc
 
         if (claim is { } idClaim)
         {
-            return (idClaim.Type, idClaim.Value);
+            return (idClaim.Type, idClaim.Value, idClaim.Issuer);
         }
 
         return null;

src/ModelContextProtocol.AspNetCore/README.md

@@ -30,7 +30,7 @@ dotnet add package ModelContextProtocol.AspNetCore --prerelease
 
 ```csharp
 // Program.cs
-?using ModelContextProtocol.Server;
+using ModelContextProtocol.Server;
 using System.ComponentModel;
 
 var builder = WebApplication.CreateBuilder(args);