Change one URL.
If your host, IDE or agent already reads the official MCP registry, it can read tashan instead and get the same payload with a measurement attached. No SDK, no integration, no awareness of us beyond a base URL.
↓
tashan.sh/v0.1/servers
What you get that you did not have
Every entry keeps its registry shape and gains one namespaced block, so nothing you already parse changes:
"io.modelcontextprotocol.registry/official": { … unchanged … },
"sh.tashan/measurement": {
"score": 86, "adoption": 84, "upkeep": 98, "freshness": 97,
"vitality": "active", "expertise": "solid",
"evidence": "32,517 npm downloads/week",
"url": "https://tashan.sh/capability/…", "measured_at": "…"
}
}
5,278 measured servers today. Unscored servers are absent rather than zero — we never publish a number we did not measure.
One score, one request
If you only need a number at decision time, /v0.1/scores is a flat map — name to [score, vitality, evidence] — so you are not pulling the full catalogue to check one package.
Terms
- Free and unmetered. No key, no quota, CC BY 4.0. We want you calling it — that is the distribution.
- Never pay-to-rank. Nobody can buy a score, a position or a removal. If that ever changed, the number would be worth nothing to you.
- Not a security audit. A tashan score measures adoption and upkeep. It is not a CVE scan or a code review, and it should not be presented to your users as one.
If you need a promise
The static files above carry no uptime or schema-stability commitment, because they are files. If you are shipping tashan inside a product and need a keyed endpoint, versioning guarantees or change webhooks, that is a conversation: [email protected].