Loading ToolBench

Reading the current corpus…

nmcp MCP server · D · ToolBench

← Browse

nmcp

github.com/nwrx/nmcp

A Kubernetes operator for managing Model Context Protocol (MCP) servers in Kubernetes environments

<=2025-11-25STREAMABLE_HTTP5 tools

57/100

Definition Quality71

Protocol Readiness62

Supportability31

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging

Deprecated protocol patterns detected

Summary

nmcp is a Kubernetes operator for managing MCP servers. It exposes 5 tools for server lifecycle management (search, get, create, update, delete) via HTTP. All tools have descriptions and parameter schemas are visible in server_docs.rs. However, several quality gaps prevent a higher score: (1) Parameter descriptions are present but often generic, lacking actionable detail about constraints and formats. (2) Output schemas are not explicitly documented, the code returns MCPServerBody structs but the response structure is not formally specified in tool definitions. (3) Tool names are clear and action-oriented, but descriptions could be more specific about when to use each vs alternatives. (4) Error handling exists but error messages are not visible in the provided code, unclear whether recovery guidance is provided. (5) No tool annotations (readOnlyHint/destructiveHint) are present despite clear risk levels.

Tools (5)

createServerwritesource verified70/100

Creates a new `MCPServer` resource with the specified name and configuration. This initiates deployment of a Kubernetes Pod and, if applicable, a Service based on the server's transport type (SSE or STDIO).

deleteServerdestructivesource verified70/100

Removes an `MCPServer` and cleans up all its associated Kubernetes resources. This includes terminating the server Pod and deleting any associated Service resources, ensuring complete cleanup.

getServerByNameread onlysource verified75/100

Retrieves a specific `MCPServer` by name, returning its complete configuration and current status. This includes the server's pool assignment, container details, transport configuration, and running state.

searchServersread onlysource verified57/100

Retrieves a list of all `MCPServer` resources in the current namespace. Returns detailed information about each server, including its configuration, current status, and associated pool.

updateServerByNamewritesource verified68/100

Updates the configuration of an existing `MCPServer`. This allows modifying the container image, arguments, environment variables, transport configuration, and other settings while maintaining the server's identity.

Issues (6)

HIGHtool-output-schema ↗

Output schemas not documented in tool definitions. Tools return MCPServerBody but response structure is not formally specified, forcing LLMs to infer field names and types.

searchServersgetServerByNamecreateServerupdateServerByNamedeleteServer

HIGHtool-annotations ↗

Tool annotations missing. Despite clear risk levels (READ_ONLY, WRITE, DESTRUCTIVE), tools lack readOnlyHint, destructiveHint, and idempotentHint annotations in schema, preventing agents from reasoning about side effects.

searchServersgetServerByNamecreateServerdeleteServerupdateServerByName

HIGHconstrained-input ↗

Parameter descriptions lack actionable constraints. 'transport' param accepts object but no format/schema documented; 'env' param is array but element structure undefined; 'idleTimeout' is integer but min/max bounds not stated.

createServerupdateServerByName

Recommendations

Add formal output schema documentation to all tools. Example: 'Returns MCPServerBody with fields: id (string, UUID), name (string), pool (string), image (string), status (MCPServerStatus object containing phase, conditions, replicas).'
Integrate tool annotations: add 'readOnlyHint: true' to searchServers and getServerByName; add 'destructiveHint: true' to deleteServer; add 'idempotentHint: true' to createServer/updateServerByName if idempotent-on-conflict.
Expand parameter descriptions with constraints. For 'transport' param: 'Transport configuration object. Required fields: type (string, enum: stdio|sse|streamable-http). For SSE/streamable-http, include url (string) and optional headers (object).' For 'idleTimeout': 'Server idle timeout in seconds (30-3600, default 300). Servers idle longer than this are terminated.'
Implement pagination for searchServers: add optional 'limit' (1-100, default 20) and 'offset' (0+, default 0) parameters. Return response with fields: servers (array of MCPServerBody), total (integer), hasMore (boolean).
Add error recovery guidance in response. Example: 'If createServer fails with "pool not found", call searchPools first to verify the pool exists. If "image not found", verify image is accessible in your container registry.'
Add dry-run pattern to deleteServer: add optional 'dryRun' (boolean, default false) parameter. When true, validate deletion would succeed but do not actually delete. Response should indicate 'dryRun: true, wouldDelete: {pods: [pod-name], services: [svc-name]}'.

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

↓ 7 points across a rubric change (v1 → v2)

57/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-22	D	57	<=2025-11-25	v2
2026-03-09	C	64	-	v1