accelbyte-ai-plugins vs Opedd — Licensed Content for AI
accelbyte-ai-plugins is a plugin bundle for AI coding tools published by AccelByte. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). Opedd — Licensed Content for AI is an MCP server published by opedd.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  accelbyte-ai-plugins |   Opedd — Licensed Content for AI |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.6.12 Forks (GitHub): 3 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.11.1 Downloads/month (npm): 1 501 Downloads/week (npm): 258 Forks (GitHub): 0 Stars (GitHub): 1 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
| Fact | accelbyte-ai-plugins | Opedd — Licensed Content for AI |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 4 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.opedd.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 6, secrets among them: 5 |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/accelbyte/ai-plugins | github.com/opedd/opedd-mcp |
| Changes in the last 7 days (differs) | 2 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 45 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
accelbyte-ai-plugins
Public AI coding agents, skills, and MCP servers for AccelByte.
Opedd — Licensed Content for AI
Licensed, rights-cleared content for AI agents - verifiable license keys + EU AI Act attestation.
How to run each
accelbyte-ai-plugins As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install accelbyte-ai-plugins@claude-communityOpedd — Licensed Content for AI As a remote MCP server
claude mcp add --transport http opedd-mcp https://mcp.opedd.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: OPEDD_ACCESS_KEY (secret), OPEDD_BUYER_JWT (secret), OPEDD_BUYER_TOKEN (secret), OPEDD_PAYMENT_METHOD_ID (secret), OPEDD_PUB_BEARER (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Opedd — Licensed Content for AI 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
The marketplaces of accelbyte-ai-plugins publish no settings it asks for, so we do not compare settings.
What it can do: accelbyte-ai-plugins · What it can do: Opedd — Licensed Content for AI · 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 public marketplace files in GitHub repositories of their authors. 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.