Ext Ops Panel
Open dashboard
Comparison

Box vs LayerOne (DocX + Sign)

Box is an MCP server published by dgageot. Marketplaces we read that list it: 1 (Docker MCP Catalog). LayerOne (DocX + Sign) is an MCP server published by GOLayerone. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceBoxLayerOne (DocX + Sign)
Docker MCP Catalog Listed
Version: sha256:4db7963505c2
Forks (GitHub): 0
Pulls (Docker Hub): 18 523
Stars (Docker Hub): 3
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (npm): 137
Downloads/week (npm): 25
Forks (GitHub): 0
Stars (GitHub): 0
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

Box vs LayerOne (DocX + Sign)
FactBoxLayerOne (DocX + Sign)
Marketplaces that list it11
Stars (GitHub)00
Pulls (Docker Hub) (differs)18 523No figure on Docker Hub
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/box)On your machine (layerone-mcp)
Transportstdiostdio
Tools it declares (differs)12Not published
Environment variables it asks for (differs)2, secrets among them: 12, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/dgageot/mcp-server-boxgithub.com/golayerone/layerone-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

Box

In its own words, on Docker MCP Catalog:

An MCP server capable of interacting with the Box API.

LayerOne (DocX + Sign)

In its own words, on Official MCP Registry:

MCP server for LayerOne DocX (documents & Factur-X) and Sign (e-signature) APIs.

How to run each

Box As a local MCP server: Docker image

Claude Code
claude mcp add --env "BOX_CLIENT_SECRET=<YOUR_BOX_CLIENT_SECRET>" --transport stdio box -- docker run -i --rm -e BOX_CLIENT_SECRET mcp/box

Requires: BOX_CLIENT_SECRET (secret)

LayerOne (DocX + Sign) As a local MCP server: npm package

Claude Code
claude mcp add --env "DOCX_API_KEY=<YOUR_DOCX_API_KEY>" --env "SIGN_API_KEY=<YOUR_SIGN_API_KEY>" --transport stdio layerone -- npx -y layerone-mcp

Requires: DOCX_API_KEY (secret), SIGN_API_KEY (secret)

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

Tools each declares

The marketplaces of LayerOne (DocX + Sign) publish no list of tools, so we do not compare tools.

Settings each asks for

Only Box asks for

  • BOX_CLIENT_ID
  • BOX_CLIENT_SECRET (secret)

Only LayerOne (DocX + Sign) asks for

  • DOCX_API_KEY (secret)
  • SIGN_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Box · What it can do: LayerOne (DocX + Sign) · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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