Question 1

Is Modelcontextprotocol · @modelcontextprotocol or Shipmail better?

Accepted Answer

Modelcontextprotocol · @modelcontextprotocol scores 84.0 and Shipmail scores 71.0 on the tashan score, which measures upkeep and freshness gated by real adoption. Neither number is a security audit and neither can be bought. The gap is wide enough to be decisive.

Question 2

Are Modelcontextprotocol · @modelcontextprotocol and Shipmail safe to install?

Accepted Answer

Modelcontextprotocol · @modelcontextprotocol: no known advisories, no build provenance. Shipmail: no known advisories, no build provenance. Every capability tashan measures is checked against the OSV advisory database at the version you would install today, for install-time scripts and for build provenance. The audit reads public evidence and never executes anything.

Question 3

How were these two compared?

Accepted Answer

Both were measured on the same day by the same scorer, from public signal only — npm download volume and publish cadence, repository activity, maintainer count and registry status. Nobody can pay to change a score, a rank or a listing.

	Modelcontextprotocol · @modelcontextprotocol	Shipmail	what it means
tashan score	84	71	upkeep + freshness, gated by adoption
Adoption evidence	458k/wk	2k/wk	the raw public signal the score came from
Last release	active	active	npm publish or repo push
Upkeep	91	73	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, no build provenance	a summary — the full audit, free, is on each dossier
Licence	—	—
Maintainers	more than one	one primary	bus-factor risk

Modelcontextprotocol · @modelcontextprotocol vs Shipmail

Install either