Nx MCP
[ tools: 1 ][ checks: 12 ][ latency: 4ms ]
82/100(B)
npx -y nx-mcp@latest
check breakdown
✓Tools exposed — Server exposed 1 tool.
• nx_docs
✓Input schemas valid — All tools have a valid JSON-Schema input definition.
✓Input schema quality — Input schemas are well-typed and documented.
!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.
✓Descriptions — Every tool and parameter is clearly described.
!Tool annotations — Annotation coverage 60% (3/5 hint fields set).
Some tools set a few hints but not all of title/readOnlyHint/destructiveHint/idempotentHint/openWorldHint.
→ 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 — 1 of 1 tool(s) have no title.
• nx_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 — Server declares top-level instructions for clients.
✓Handshake + list latency — tools/list responded in 4ms.
✗Resources — Server declares the resources capability but resources/list failed.
MCP error -32601: Method not found
→ The server advertised resources support during initialize but resources/list errored or timed out.
→ Either fix the resources/list handler or remove the `resources` capability from your initialize response.
add the badge
Paste into your README:
[](https://scoremcp.dev/servers/nx-mcp)