dotnet-mcp-server-blueprint
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRANSPORT | No | Transport mode. Set to `http` to enable Streamable HTTP at `/mcp`; defaults to `stdio`. | stdio |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| evaluate_mcp_trust_boundaryB | Evaluates an MCP server deployment configuration against trust-boundary best practices. |
| validate_server_manifestB | Validates a server.json payload against Official MCP Registry constraints. |
| generate_tool_policy_summaryB | Classifies an MCP tool into a least-privilege capability scope and approval policy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| mcp_security_review | Generates a structured security audit prompt for an MCP server implementation. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| mcp_production_checklist | Production checklist covering transport isolation, stderr logging, least privilege, and supply-chain verification. |
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.