Skip to main content
Glama
dotnet-mcp-server-blueprint

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:


Architecture Highlights

  • Dual Transport Support:

    • Standard I/O (stdio) by default for local desktop/IDE hosts (Claude Code, Antigravity, Cursor, VS Code), with strict stderr-only diagnostics so stdout stays pure JSON-RPC.

    • Streamable HTTP (--http / MCP_TRANSPORT=http) exposing /mcp alongside /health for 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.json for the Official MCP Registry and glama.json + multi-stage Dockerfile for Glama.ai.


Related MCP server: Learn MCP Server

Quick Start

Run via .NET Tool (stdio)

dotnet tool install --global RazvanApps.McpServer.Blueprint
razvanapps-mcp-blueprint

Run locally over Streamable HTTP

dotnet run --project src/RazvanApps.McpServer.Blueprint -- --http

MCP 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 ./artifacts

License

MIT — Răzvan Mareș (RazvanApps)

Available Tools

3 tools
evaluate_mcp_trust_boundaryEvaluate MCP Trust BoundaryB
Read-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 SummaryB
Read-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 ManifestB
Read-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

    B3.3/5.0

    Scored across 3 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      B
      quality
      D
      maintenance
      A 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
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      -
    • F
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server template built with mcp-framework, providing a foundation for creating custom tools and publishing npm packages.
      2
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Open-source .NET library/SDK that turns any .NET application into an MCP server (in-app plugin + SignalR server, stdio/HTTP transport).
      21
      Apache 2.0