Ext Ops Panel
Open dashboard
Comparison

assay vs SmartBear MCP

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. SmartBear MCP is an MCP server published by smartbear.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-29. 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

Where each is published
MarketplaceassaySmartBear MCP
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: 0.42.0
Downloads/month (npm): 34 553
Downloads/week (npm): 6 200
Forks (GitHub): 51
Stars (GitHub): 44
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:8a64acae01b6
Forks (GitHub): 51
Pulls (Docker Hub): 14 756
Stars (Docker Hub): 0
Stars (GitHub): 44
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

assay vs SmartBear MCP
Factassayno longer listed · SmartBear MCP
Marketplaces that list it (differs)02
Stars (GitHub) (differs)1344
Pulls (Docker Hub) (differs)No figure on Docker Hub14 756
Forks (GitHub) (differs)351
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declares (differs)Not published160
Environment variables it asks for (differs)Not published17, secrets among them: 10
Parts of the bundle (differs)2Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/rul1an/assaygithub.com/smartbear/smartbear-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 400 (5 days ago)

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.

  • sosa-compliance-checker

    Audit your Claude plugins, skills, and coding agents against the SOSA methodology — Supervised Orchestrated Secured Agents. Scans your entire plugin ecosystem and evaluates each…

    by MSApps-Mobile · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • DeepEval

    Skills for adding DeepEval evaluations, tracing, datasets, Confident AI reports, and iterative improvement loops to AI applications.

    by confident-ai · Plugin bundle

    Listed on: Claude Code: claude-plugins-official, Community GitHub marketplaces · Describes nearly the same job

  • opik

    All the tooling you need to add observability to Claude Code and your agents

    by Comet ML · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • grainulator

    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…

    by grainulation · Plugin bundle

    Listed on: Claude Code: claude-plugins-community, Community GitHub marketplaces · Describes nearly the same job

  • memoriant-eval-sandbox-skill

    AI agent evaluation sandbox for Claude Code. Holdout scenario testing with Doer/Judge/Adversary/Observer roles, probabilistic satisfaction scoring, and append-only JSONL audit…

    by NathanMaine · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • mcp-audit io.github.archonics/mcp-audit

    Free context-engineering audits for AI agents. BYOK Anthropic key. Top-3 findings per scan.

    by archonics · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

assay

In its own words, on Community GitHub marketplaces:

Connect Claude Code to Assay's MCP policy and evidence tools and golden-path skill.

SmartBear MCP

In its own words, on Official MCP Registry:

MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.

How to run each

assay

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

SmartBear MCP As a remote MCP server

Claude Code
claude mcp add --transport http smartbear-mcp https://bugsnag.mcp.smartbear.com/mcp

Requires: BEARQ_API_TOKEN (secret), BUGSNAG_AUTH_TOKEN (secret), PACT_BROKER_PASSWORD (secret), PACT_BROKER_TOKEN (secret), QTM4J_API_KEY (secret), QTM4J_AUTOMATION_API_KEY (secret), REFLECT_API_TOKEN (secret), SWAGGER_API_KEY (secret), SWAGGER_FUNCTIONAL_TESTING_API_TOKEN (secret), ZEPHYR_API_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only SmartBear MCP has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of assay publish no list of tools, so we do not compare tools.

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: SmartBear MCP · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built