npm package ws has 241560546 weekly downloads but sdk
io.github.nexus-mcp-infra/npm-package-ws-has-241560546-weekly-downloads-but-sdk
Stateful WebSocket session registry with per-connection Shannon entropy delta tracking for schema di
— the operator's own registry description reported
Publisher io.github.nexus-mcp-infra · first seen 2026-08-12 · endpoint https://npm-package-ws-has-241560546-w-production.up.railway.app/mcp
Dependency rating derived
allow — alive & usable · action ● · V n/a
Cluster mid-solo · distinctiveness 0.537 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.
🔏 Signed receipt rr_6ffe75e2d1f2dcc67b92a094 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.
● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →
History observed
Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.
changelog (1 events)
| date | type | what changed |
|---|---|---|
| 2026-08-12 | outcome | first probe: ok_tools |
What kind of tools these are derived
Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):
| nature | tools | meaning | what checking applies |
|---|---|---|---|
| action | 4 | changes the world | no true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions |
| unclassified | 1 | not classifiable from its text | Tier-1 only until its tools describe themselves |
Tools last seen observed
Harness readiness observed
Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.
| legibility check | tools passing | ok |
|---|---|---|
| name is clear & specific | 5/5 | ✓ |
| has a description | 5/5 | ✓ |
| description is substantive | 5/5 | ✓ |
| parameters are typed | 5/5 | ✓ |
| parameters are described | 5/5 | ✓ |
5 of 5 tools graded · 5 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.
Truth checks observed
Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.
Protocol conformance observed
Capabilities: experimental prompts resources tools
Drift observed
No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.
raw probe records
| probed (UTC) | outcome | http | ms | protocol |
|---|---|---|---|---|
| 2026-08-14T19:59:53Z | ok_tools | 200 | 94 | 2025-06-18 |
| 2026-08-12T05:35:10Z | ok_tools | 200 | 91 | 2025-06-18 |
Watch or embed this verdict
Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:
[](https://robinsaige.com/s/io.github.nexus-mcp-infra/npm-package-ws-has-241560546-weekly-downloads-but-sdk)
Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.