Ext Ops Panel
Open dashboard
Comparison

Claude Perms vs SmartBear MCP

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

Claude Perms is a plugin bundle for AI coding tools published by b-open-io. 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-21. 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
MarketplaceClaude PermsSmartBear MCP
Community marketplace b-open-io/claude-plugins Removed on 2026-10-17
Version: 0.1.1
Forks (GitHub): 0
Stars (GitHub): 0
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 437
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

Claude Perms vs SmartBear MCP
FactClaude Permsno longer listed · SmartBear MCP
Marketplaces that list it (differs)02
Stars (GitHub) (differs)044
Pulls (Docker Hub) (differs)No figure on Docker Hub14 437
Forks (GitHub) (differs)051
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
Licence (differs)Not statedMIT
Repository (differs)github.com/b-open-io/claude-permsgithub.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 (4 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 Claude Perms

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

  • aport-guardrails

    Security guardrails for Claude Code. Intercepts every tool call via PreToolUse hook and evaluates it against your Open Agent Passport (OAP) policy before execution. Blocks…

    by aporthq · Plugin bundle

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

  • clawkeeper

    Frictionless security, compliance, and threat detection for Claude Code and Co-Work. Advanced Behavioral detection patterns catch credential exfiltration, reverse shells, prompt…

    by rad-security · Plugin bundle

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

  • claude-code-organizer io.github.mcpware/claude-code-organizer

    Organize Claude Code memories, skills, MCP servers, commands, agents, rules via drag-and-drop.

    by mcpware · MCP server

    Listed on: Official MCP Registry, Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-account-guard

    A Claude Code plugin that warns or blocks prompts when the active Claude account doesn't match the expected account for the current directory. Useful for teams or individuals who…

    by fseitun · Plugin bundle

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

  • promptbook

    Track your Claude Code sessions automatically. Promptbook records prompts, token usage, build time, lines changed, and primary language, then turns each session into a shareable…

    by promptbookgg · Plugin bundle

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

  • reco

    Reco SaaS & AI security — query app risks, shadow IT, AI agents, user posture, and access events directly from Claude Code

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

Claude Perms

In its own words, on Community GitHub marketplaces:

TUI permission analyzer - visualize tool usage frequency, approve/deny counts, and manage Claude Code permissions with live diff previews

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

Claude Perms

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

Settings each asks for

The marketplaces of Claude Perms publish no settings it asks for, so we do not compare settings.

What it can do: Claude Perms · 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