assay vs Entroly
assay is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑27.
assay is a plugin bundle for AI coding tools published by Roel Schuurkes. No marketplace we read lists it any more. Entroly is an MCP server published by juyterman1000. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-11-15. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Entroly | |
|---|---|---|
| Community marketplace rul1an/assay | Removed on 2026-10-27 Version: not stated Forks (GitHub): 3 Stars (GitHub): 13 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.90 Downloads/month (PyPI): 1 455 Downloads/week (PyPI): 394 Forks (GitHub): 74 Stars (GitHub): 486 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.0.88 Downloads/month (npm): 923 Downloads/week (npm): 348 Forks (GitHub): 74 Stars (GitHub): 486 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | assayno longer listed · | Entroly |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 3 |
| Stars (GitHub) (differs) | 13 | 486 |
| Forks (GitHub) (differs) | 3 | 74 |
| Last release (differs) | Not published | 2026-11-15 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (entroly) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 1 |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | 2 | 4 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/rul1an/assay | github.com/juyterman1000/entroly |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of assay
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Audit your Claude plugins, skills, and coding agents against the SOSA methodology — Supervised Orchestrated Secured Agents. Scans your entire plugin ecosystem and evaluates each…
-
Skills for adding DeepEval evaluations, tracing, datasets, Confident AI reports, and iterative improvement loops to AI applications.
-
Agent skills for observing and evaluating LLM applications with LangSmith
-
Research sprint orchestrator for Claude Code. Ask a question, get a decision-ready brief — every finding is tracked as a typed claim, adversarially challenged, confidence-graded…
-
Persistent reviewed research and engineering runtime
-
Persistent reviewed research and engineering runtime
What each says it does
assay
Connect Claude Code to Assay's MCP policy and evidence tools and golden-path skill.
Entroly
Context Assurance for AI agents: context engineering, AI cost optimization, verification.
How to run each
assay
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Entroly As a local MCP server: PyPI package
claude mcp add --transport stdio entroly -- uvx entrolyCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of assay publish no settings it asks for, so we do not compare settings.
What it can do: assay · What it can do: Entroly · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.