Context7
[ tools: 2 ][ checks: 13 ][ latency: 7ms ]
87/100(B)
npx -y @upstash/context7-mcp
check breakdown
✓Tools exposed — Server exposed 2 tools.
• resolve-library-id
• query-docs
✓Input schemas valid — All tools have a valid JSON-Schema input definition.
!Input schema quality — 2 schema-quality issue(s) across 2 tool(s).
resolve-library-id: inputSchema.additionalProperties is not set to false (extra args pass through silently)
query-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.
• "resolve-library-id"
• "query-docs"
✓Descriptions — Every tool and parameter is clearly described.
!Tool annotations — Annotation coverage 80% (8/10 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 — All tools declare a human-readable title.
✓Server instructions — Server declares top-level instructions for clients.
✓Handshake + list latency — tools/list responded in 7ms.
!Prompts — Server declares the prompts capability but exposes 0 prompts.
→ If you don't actually offer prompts, remove the `prompts` capability from your initialize response.
→ Otherwise, register at least one prompt via your prompts/list handler.
!Resources — Server declares the resources capability but exposes 0 resources.
→ If you don't actually offer resources, remove the `resources` capability from your initialize response.
→ Otherwise, register at least one resource (or resource template) via your resources/list handler.
add the badge
Paste into your README:
[](https://scoremcp.dev/servers/context7)