Question 1

Is Postgres · modelcontextprotocol or Run402 better?

Accepted Answer

Run402 scores 69.0 and Postgres · modelcontextprotocol scores 18.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 Postgres · modelcontextprotocol and Run402 safe to install?

Accepted Answer

Postgres · modelcontextprotocol: no known advisories, no build provenance. Run402: no known advisories. 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.

	Postgres · modelcontextprotocol	Run402	what it means
tashan score	18	69	upkeep + freshness, gated by adoption
Adoption evidence	127k/wk	1k/wk	the raw public signal the score came from
Last release	abandoned	active	npm publish or repo push
Upkeep	18	73	cadence, maintainers, status
Expertise grade	not graded	solid	an LLM read of its own documentation against a fixed rubric
Security audit	no known advisories, no build provenance	no known advisories	existence of findings is always free; the detail a licence buys is on each dossier
Licence	MIT	—
Maintainers	more than one	one primary	bus-factor risk

Postgres · modelcontextprotocol vs Run402

Install either