Knip
[ tools: 2 ][ checks: 13 ][ latency: 8ms ]
85/100(B)
npx -y @knip/mcp
check breakdown
✓Tools exposed — Server exposed 2 tools.
• knip-run
• knip-docs
✓Input schemas valid — All tools have a valid JSON-Schema input definition.
!Input schema quality — 3 schema-quality issue(s) across 2 tool(s).
knip-run: no "required" array (which params are mandatory?)
knip-run: inputSchema.additionalProperties is not set to false (extra args pass through silently)
knip-docs: inputSchema.additionalProperties is not set to false (extra args pass through silently)
→ Declare `required` for every schema that has properties, so agents know which params are mandatory.
→ Give every property a `description` and a concrete `type` (avoid bare `{}` placeholders).
→ Set `additionalProperties: false` on the top-level inputSchema so models can't silently pass extra, unvalidated arguments.
!Output schemas — No tools declare an outputSchema.
→ Optional: declare outputSchema for tools with structured results so agents can validate/parse output reliably.
✓Duplicate tool names — All tool names are unique.
✓Tool naming — All tool names use spec-legal characters.
Advisory (not scored): 2 name(s) aren't lower_snake_case — consistent lower_snake_case tends to help model tool-selection reliability, though mixed case, digits, underscores, hyphens, and dots are all spec-legal.
• "knip-run"
• "knip-docs"
✓Descriptions — Every tool and parameter is clearly described.
!Tool annotations — Annotation coverage 0% (0/10 hint fields set).
• knip-run: no annotations at all
• knip-docs: no annotations at all
→ Add annotations: title, readOnlyHint, destructiveHint, idempotentHint, openWorldHint.
→ These let clients gate risky calls and give agents/users a friendly display name — optional but valuable.
!Tool titles — 2 of 2 tool(s) have no title.
• knip-run: no top-level title (or annotations.title)
• knip-docs: no top-level title (or annotations.title)
→ Declare a top-level `title` on each tool — it gives clients a friendly display name distinct from the machine-readable `name`.
→ `annotations.title` (the older location) is also accepted, but the top-level `title` field is now the spec-preferred place for it.
!Server instructions — No top-level instructions declared.
→ Declare instructions to guide agents on when/how to use this server.
→ Return a non-empty `instructions` string in your InitializeResult — most SDKs let you set this alongside serverInfo.
✓Handshake + list latency — tools/list responded in 8ms.
✓Prompts — All 1 prompt(s) are well-named and documented.
✓Resources — All 16 resource(s)/template(s) are well-described.
add the badge
Paste into your README:
[](https://scoremcp.dev/servers/knip-mcp)