Ext Ops Panel
Open dashboard
Comparison

eterdis-pre-mortem vs SmartBear MCP

eterdis-pre-mortem is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.

eterdis-pre-mortem is a plugin bundle for AI coding tools published by Eterdis AS. 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-26. 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
Marketplaceeterdis-pre-mortemSmartBear MCP
Community marketplace eterdis/strategy-skills Removed on 2026-10-26
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 10
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): 51
Stars (GitHub): 44
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:8a64acae01b6
Forks (GitHub): 51
Pulls (Docker Hub): 14 660
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

eterdis-pre-mortem vs SmartBear MCP
Facteterdis-pre-mortemno longer listed · SmartBear MCP
Marketplaces that list it (differs)02
Stars (GitHub) (differs)1044
Pulls (Docker Hub) (differs)No figure on Docker Hub14 660
Forks (GitHub) (differs)151
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
Licence (differs)CC-BY-4.0MIT
Repository (differs)github.com/eterdis/strategy-skillsgithub.com/smartbear/smartbear-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-132026-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 eterdis-pre-mortem

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

  • itk-premortem

    Imagine a future failure to uncover risks and strengthen plans before committing. Best for stress-testing OKRs, roadmaps, and launch plans.

    by deanpeters · Plugin bundle

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

  • stress-test

    Adversarially stress-test technical plans by verifying claims against real docs, running POC code, and updating the plan before you build.

    by Gary Basin · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes a related job

  • epic-hypothesis

    Frame an epic as a testable hypothesis with target user, outcome, and validation.

    by deanpeters · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes a related job

  • contrarian

    Steel-mans the proposal, audits its assumptions, runs a pre-mortem and inversion, and returns severity-rated findings with a failure scenario and a recommendation for each, plus a…

    by aaddrick · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes a related job

  • critical-thinking-tools

    Critical Thinking Tools is a science-backed Claude Code plugin from Cognitive Bias Lab that helps users reason more clearly about decisions, beliefs, plans, forecasts, and…

    by cognitive-bias-lab · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes a related job

  • spec-driven-dev

    Explore directions through research-led brainstorming, write comprehensive specs, and implement them with risk-first subagent workflows and live verification

    by Daan Ferdinandusse · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes a related job

Its card, with similar plugins by marketplace

What each says it does

eterdis-pre-mortem

In its own words, on Community GitHub marketplaces:

Stress-test plans by imagining they've already failed. Six failure categories, the monkey test, and concrete adjustments.

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

eterdis-pre-mortem

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

Settings each asks for

The marketplaces of eterdis-pre-mortem publish no settings it asks for, so we do not compare settings.

What it can do: eterdis-pre-mortem · 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