Ext Ops Panel
Open dashboard
Comparison

Effect vs async-fixer

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

Effect is an MCP server published by tim-smart. Marketplaces we read that list it: 1 (Docker MCP Catalog). async-fixer is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-18. 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
MarketplaceEffectasync-fixer
Docker MCP Catalog Listed
Version: sha256:a0e077abc890
Forks (GitHub): 13
Pulls (Docker Hub): 12 933
Stars (Docker Hub): 0
Stars (GitHub): 238
Not marked · First seen
Not listed
Community marketplace barnburner121/claude-plugin-marketplace Not listed Removed on 2026-10-18
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
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

Effect vs async-fixer
FactEffectasync-fixerno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)2383
Pulls (Docker Hub) (differs)12 933No figure on Docker Hub
Forks (GitHub) (differs)130
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/effect-mcp)On your machine (@barnburner121/plugin-hub-mcp)
Transport (differs)stdioNot stated
Tools it declares (differs)2Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle2
LicenceMITMIT
Repository (differs)github.com/tim-smart/effect-mcpgithub.com/barnburner121/claude-plugin-marketplace
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-10-14

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 async-fixer

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

  • bug-detective

    Systematically debug issues with step-by-step troubleshooting approaches.

    by Anonymous · Plugin bundle

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

  • Mneme

    Prevent, catch, and verify architectural violations while Claude Code works.

    by Mneme HQ · Plugin bundle

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

  • debugger

    Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

    by Anand Tyagi · Plugin bundle

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

  • debug-session

    Ask Claude Code to help you debug an issue

    by Anand Tyagi · Plugin bundle

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

  • Predictive Debugger

    Predicts where JavaScript and TypeScript code will fail at runtime, for coding agents.

    by SpeedosDK · MCP server

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

  • ff-review

    Plugin description Code quality review plugin based on Frontend Fundamentals 4 principles (readability, predictability, cohesion, coupling). Supports React and Angular with…

    by rrkkee015 · 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

Effect

In its own words, on Docker MCP Catalog:

Tools and resources for writing Effect code in Typescript.

async-fixer

In its own words, on Community GitHub marketplaces:

Detect async/await anti-patterns and race conditions

How to run each

Effect As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio effect-mcp -- docker run -i --rm mcp/effect-mcp

async-fixer

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

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

Tools each declares

The marketplaces of async-fixer publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Effect · What it can do: async-fixer · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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