dotnet-mcp-server-blueprint
.NET 10 MCP Server Blueprint
A production-ready reference implementation of a Model Context Protocol (MCP) server built on .NET 10 and the official C# SDK (ModelContextProtocol & ModelContextProtocol.AspNetCore).
Designed as an end-to-end companion to:
Build a Production-Ready MCP Server in C#: Tools, Trust, and Transport
Inside the Official MCP Registry: A Supply Chain for AI Tools
Architecture Highlights
Dual Transport Support:
Standard I/O (
stdio) by default for local desktop/IDE hosts (Claude Code,Antigravity,Cursor,VS Code), with strictstderr-only diagnostics sostdoutstays pure JSON-RPC.Streamable HTTP (
--http/MCP_TRANSPORT=http) exposing/mcpalongside/healthfor containerized or remote deployments.
Typed Domain Logic & Tool Annotations:
Explicit
[McpServerTool(ReadOnly = true, Idempotent = true, Destructive = false, OpenWorld = false)]capabilities.Three deterministic governance tools:
evaluate_mcp_trust_boundary,validate_server_manifest,generate_tool_policy_summary.Built-in resource (
architecture://mcp/checklist) and prompt (mcp_security_review).
Registry-Ready Supply Chain:
Packaged as a cross-platform .NET tool (
RazvanApps.McpServer.Blueprint).Ships valid
server.jsonfor the Official MCP Registry andglama.json+ multi-stageDockerfilefor Glama.ai.
Related MCP server: Learn MCP Server
Quick Start
Run via .NET Tool (stdio)
dotnet tool install --global RazvanApps.McpServer.Blueprint
razvanapps-mcp-blueprintRun locally over Streamable HTTP
dotnet run --project src/RazvanApps.McpServer.Blueprint -- --httpMCP endpoint: http://localhost:5000/mcp
Health endpoint: http://localhost:5000/health
Client Configuration (mcp.json)
{
"mcpServers": {
"razvanapps-mcp-blueprint": {
"command": "razvanapps-mcp-blueprint"
}
}
}Verification
dotnet test -c Release
dotnet pack src/RazvanApps.McpServer.Blueprint -c Release -o ./artifactsLicense
Available Tools
3 toolsevaluate_mcp_trust_boundaryEvaluate MCP Trust BoundaryBRead-onlyIdempotent
Evaluates an MCP server deployment configuration against trust-boundary best practices.
Inputs: transport (required), isReadOnly (required), validatesInputs (required), executesShellCommands (required), +2 more.
generate_tool_policy_summaryGenerate Tool Policy SummaryBRead-onlyIdempotent
Classifies an MCP tool into a least-privilege capability scope and approval policy.
Inputs: toolName (required), isReadOnly (required), isDestructive (required), touchesExternalNetwork (required).
validate_server_manifestValidate Official MCP Registry ManifestBRead-onlyIdempotent
Validates a server.json payload against Official MCP Registry constraints.
Inputs: serverJson (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool operates on a different artifact: a deployment configuration (trust boundary), a server.json manifest (registry validation), and an individual tool (capability/approval policy). The only mild overlap is the evaluate/validate verb pair, which an agent could briefly conflate, but the target objects are clearly distinguished in the descriptions.
All names are snake_case and verb-first (evaluate_, validate_, generate_), which is predictable. The third name, generate_tool_policy_summary, is a longer noun-phrase construction and its description says 'classifies' rather than 'generates a summary', a small mismatch with the pattern and stated action.
Three tools is thin for a server framed as a 'blueprint' covering trust, registry, and policy concerns. Each tool does earn its place, but the surface feels like a subset of a larger governance workflow rather than a well-scoped set.
The surface covers assessment (trust boundary), validation (manifest), and classification (tool policy), but there is no scaffolding/generation of a server.json or deployment config, no remediation or fix path after a failed validation, and no way to enumerate or look up registry entries. Agents can evaluate artifacts but cannot create or repair them, leaving a dead end in the lifecycle.
Maintenance
Related MCP Connectors
Primarily to be used as a template repository for developing MCP servers with FastMCP in Python, P…
A simple MCP server built with FastMCP and python
A simple Typescript MCP server built using the official MCP Typescript SDK and smithery/cli. This…
Related MCP Servers
- FlicenseBqualityDmaintenanceA basic Model Context Protocol (MCP) server implementation that provides a foundation for MCP server development. The README doesn't specify particular functionality, suggesting it may be a template or starting point for building custom MCP servers.1-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server designed for learning and experimentation. It provides a foundational setup for developers to build, run, and debug MCP server implementations using Node.js.-
- FlicenseCqualityDmaintenanceA Model Context Protocol (MCP) server template built with mcp-framework, providing a foundation for creating custom tools and publishing npm packages.2-
- AlicenseNot gradedqualityBmaintenanceOpen-source .NET library/SDK that turns any .NET application into an MCP server (in-app plugin + SignalR server, stdio/HTTP transport).21Apache 2.0