Ext Ops Panel
Open dashboard
Comparison

seo-assistant-silverbee vs Autonomy x402 Tools

seo-assistant-silverbee is a plugin bundle for AI coding tools published by silverbee-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Autonomy x402 Tools is an MCP server published by Autonomy-Labs-Tech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceseo-assistant-silverbeeAutonomy x402 Tools
Claude Code: claude-plugins-community Listed
Version: db863ca
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

seo-assistant-silverbee vs Autonomy x402 Tools
Factseo-assistant-silverbeeAutonomy x402 Tools
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (www.autonomylabsweb.tech/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/silverbee-ai/claude-silverbee-marketplacegithub.com/autonomy-labs-tech/taskmarket-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (39 h ago)

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

seo-assistant-silverbee

In its own words, on Claude Code: claude-plugins-community:

AI-powered SEO assistant for Claude — gives Claude live access to Google Search Console, Ahrefs, DataForSEO, Google Analytics, Web Vitals, and 10+ data sources. Specialized skills for keyword research, technical SEO audits, content optimization, competitor analysis, link building, and automated workflow execution.

Autonomy x402 Tools

In its own words, on Official MCP Registry:

Pay-per-call agent tools over x402: site audits, llms.txt generation, wallet watch, catalog.

How to run each

seo-assistant-silverbee As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install seo-assistant-silverbee@claude-community

Autonomy x402 Tools As a remote MCP server

Claude Code
claude mcp add --transport http autonomy-x402-tools https://www.autonomylabsweb.tech/api/mcp

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

Only Autonomy x402 Tools has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

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

What it can do: seo-assistant-silverbee · What it can do: Autonomy x402 Tools · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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