verification-validation-and-test vs QuassLabs API
verification-validation-and-test is a plugin bundle for AI coding tools published by MathWorks. Marketplaces we read that list it: 1 (Community GitHub marketplaces). QuassLabs API is an MCP server published by quasslabs.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  QuassLabs API | |
|---|---|---|
| Community marketplace matlab/simulink-agentic-toolkit | Listed Version: 0.8.4 Forks (GitHub): 127 Stars (GitHub): 1 328 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | verification-validation-and-test | QuassLabs API |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 328 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 127 (better) | 0 (worse) |
| Last release (differs) | 2026-10-30 (worse) | 2026-11-09 (better) |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.quasslabs.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/matlab/simulink-agentic-toolkit | github.com/quasslabs/ql-api-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-27 | 2026-10-29 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 42 h ago returned HTTP 200 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
verification-validation-and-test
Author custom Model Advisor checks, run compliance reviews against industry standards (MISRA, MAB, ISO 26262, DO-178C, AUTOSAR, SLCI), author persistent, requirement-traceable Simulink Test cases, inject faults for robustness testing, perform safety analysis (FMEA, FHA, FTA), detect design errors with root cause analysis using Simulink Design Verifier, fix SLDV incompatibilities, explain missing coverage objectives, and collect quality metrics (maintainability, complexity, testing, coverage) using metric.Engine
QuassLabs API
30+ deterministic dev and delivery tools: linting, metrics, diagrams, model advice, AI-text checks.
How to run each
verification-validation-and-test As a Claude Code plugin
/plugin marketplace add matlab/simulink-agentic-toolkit
/plugin install verification-validation-and-test@simulink-agentic-toolkitQuassLabs API As a remote MCP server
claude mcp add --transport http quasslabs-api https://api.quasslabs.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only QuassLabs API has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: verification-validation-and-test · What it can do: QuassLabs API · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.