Ext Ops Panel
Open dashboard
Comparison

saas-standards vs SmartBear MCP

saas-standards is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.

saas-standards is a plugin bundle for AI coding tools published by Ossie Irondi. 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-19. 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
Marketplacesaas-standardsSmartBear MCP
Community marketplace aojdevstudio/agentic-utilities Removed on 2026-10-17
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.42.0
Downloads/month (npm): 45 350
Downloads/week (npm): 4 476
Forks (GitHub): 50
Stars (GitHub): 44
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:8a64acae01b6
Forks (GitHub): 50
Pulls (Docker Hub): 14 426
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

saas-standards vs SmartBear MCP
Factsaas-standardsno longer listed · SmartBear MCP
Marketplaces that list it (differs)02
Stars (GitHub) (differs)244
Pulls (Docker Hub) (differs)No figure on Docker Hub14 426
Forks (GitHub) (differs)050
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)1Not a bundle
LicenceMITMIT
Repository (differs)github.com/aojdevstudio/agentic-utilitiesgithub.com/smartbear/smartbear-mcp
Changes in the last 7 days (differs)40
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 400 (2 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 saas-standards

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • saas-toolkit

    The complete Claude Code toolkit for SaaS founders. 15 skills and 4 agents covering the full development cycle - from spec to launch. Build with Next.js, Supabase Auth, Vercel…

    by dangogit · Plugin bundle

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

  • great-cto

    Full SDLC pipeline with 7 agents: architecture, code review, QA, security. Two decisions per feature, the rest is automated.

    by avelikiy · Plugin bundle

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

  • MantleKit Launch Planner

    Generate MantleKit setup plans and launch-ready SaaS blueprints from a product idea.

    by mantlekit.dev · MCP server

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

  • BuildBetter

    Use BuildBetter's MCP server and bb CLI from Claude Code.

    by BuildBetter · Plugin bundle

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

  • creatio-ai-app-development-toolkit

    Creatio AI App Development Toolkit for business-plan driven Creatio app creation.

    by Creatio · Plugin bundle

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

  • solofounder

    Key features: - Clarifies before acting: asks questions with options and recommendations before designing any workflow - Dynamic flow composition: no templates, every workflow…

    by solofounder-ai · Plugin bundle

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

Its card, with similar plugins by marketplace

What each says it does

saas-standards

In its own words, on Community GitHub marketplaces:

Enforce non-negotiable SaaS application standards — signup, mandatory onboarding, route guards, database schema, backend/ORM selection, and state-management architecture. Prevents the #1 failure mode: signup flows with only email/password and zero onboarding. Bundles 4 workflow playbooks (AuditSignupFlow, ScaffoldAuth, AuditStateManagement, SelectDataLayer) plus reference docs for signup/onboarding, route guards, healthcare SaaS, data layer, and state management.

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

saas-standards

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 saas-standards publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of saas-standards publish no settings it asks for, so we do not compare settings.

What it can do: saas-standards · 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