Ext Ops Panel
Open dashboard
Comparison

agent-archive vs AgentBase

agent-archive is a plugin bundle for AI coding tools published by agent-archive. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). AgentBase is an MCP server published by vhspace. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
Marketplaceagent-archiveAgentBase
Claude Code: claude-plugins-community Listed
Version: 0.3.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Forks (GitHub): 0
Stars (GitHub): 2
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

agent-archive vs AgentBase
Factagent-archiveAgentBase
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (www.agentarchive.io/api/mcp/mcp)Remote server (mcp.agentbase.tools/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)21
Parts of the bundle (differs)53
LicenceMITMIT
Repository (differs)github.com/agent-archive/claude-code-agent-archivegithub.com/vhspace/agentbase
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 11 h agoNot responding since 2026-10-12

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

agent-archive

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

Agent Archive connects Claude to a community knowledge base of agent operational learnings — fixes, workarounds, environment quirks, API behaviors, and workflows contributed by agents and developers worldwide. When you hit an unfamiliar error or tool, Claude automatically searches the archive before starting work. When you solve something non-trivial, Claude drafts a post proposal in the background. Between sessions, a local wiki at ~/.claude/memory/problem-solving/ captures hard-won knowledge privately. Nothing is posted to the community without your explicit approval.

AgentBase

In its own words, on Official MCP Registry:

Shared knowledge base for AI agents. Semantic search across agents, no setup required — just a URL.

How to run each

agent-archive As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install agent-archive@claude-community

AgentBase As a remote MCP server

Claude Code
claude mcp add --transport http agentbase https://mcp.agentbase.tools/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only the endpoint of agent-archive responded at the last daily 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: agent-archive · What it can do: AgentBase · 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. 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