Sem vs Modelcontextprotocol · @modelcontextprotocol
Modelcontextprotocol · @modelcontextprotocol scores 14 points higher on the same evidence, which is a real separation rather than noise. 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 ›
| Sem | Modelcontextprotocol · @modelcontextprotocol | what it means | |
|---|---|---|---|
| tashan score | 70 | 84 | upkeep + freshness, gated by adoption |
| Adoption evidence | 4k/wk | 551k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 71 | 91 | cadence, maintainers, status |
| Expertise grade | deep | not graded | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, runs an install script, no build provenance | no known advisories, no build provenance | a summary — the full audit, free, is on each dossier |
| Licence | — | — | |
| Maintainers | one primary | more than one | bus-factor risk |
Install either
Sem
claude mcp add sem -- npx -y @ataraxy-labs/semModelcontextprotocol · @modelcontextprotocol
claude mcp add modelcontextprotocol-server -- npx -y @modelcontextprotocol/serverNeither 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: Sem · Modelcontextprotocol · @modelcontextprotocol.