mcp-sequentialthinking-tools
[ tools: 3 ][ checks: 12 ][ latency: 6ms ]
91/100(A)
npx -y mcp-sequentialthinking-tools
check breakdown
✓Tools exposed — Server exposed 3 tools.
• sequentialthinking_tools
• get_thinking_history
• clear_thinking_history
✓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 0% (0/15 hint fields set).
• sequentialthinking_tools: no annotations at all
• get_thinking_history: no annotations at all
• clear_thinking_history: 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 — All tools declare a human-readable title.
!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 6ms.
✓Prompts — All 1 prompt(s) are well-named and documented.
add the badge
Paste into your README:
[](https://scoremcp.dev/servers/server-sequentialthinking-tools)