SDK vs Sequential Thinking
Sequential Thinking scores 6 points higher — a narrow lead. Read the evidence rows below before treating it as decisive. Both are measured the same way, on the same day, from public evidence only — so this is a comparison of two measurements rather than two marketing pages. How we measure ›
| SDK | Sequential Thinking | what it means | |
|---|---|---|---|
| tashan score | 86 | 92 | upkeep + freshness, gated by adoption |
| Adoption evidence | 53.3m/wk | 149k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 99 | 88 | cadence, maintainers, status |
| Expertise grade | not graded | not graded | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, no build provenance | no known advisories | a summary — the full audit, free, is on each dossier |
| Licence | — | NOASSERTION | |
| Maintainers | more than one | more than one | bus-factor risk |
Install either
SDK
claude mcp add modelcontextprotocol-sdk -- npx -y @modelcontextprotocol/sdkSequential Thinking
claude mcp add sequential-thinking -- npx -y @modelcontextprotocol/server-sequential-thinkingNeither score is a security verdict — "well maintained" and "nothing known is wrong" are different claims, which is why the audit is a separate row and never folded into the number. The full audit for each — the advisory ids, the version that fixes them and anything that runs at install time — is free on its own page: SDK · Sequential Thinking.