Question 1

Is Echo or Slack · modelcontextprotocol better?

Accepted Answer

Slack · modelcontextprotocol scores 47.0 and Echo scores 21.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 Echo and Slack · modelcontextprotocol safe to install?

Accepted Answer

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

	Echo	Slack · modelcontextprotocol	what it means
tashan score	21	47	upkeep + freshness, gated by adoption
Adoption evidence	4k/wk	84k/wk	the raw public signal the score came from
Last release	abandoned	abandoned	npm publish or repo push
Upkeep	26	64	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	—	MIT
Maintainers	one primary	more than one	bus-factor risk

Echo vs Slack · modelcontextprotocol

Install either