Lodestar Stamp vs LayerOne (DocX + Sign)
Lodestar Stamp is an MCP server published by Banjo-Ventures. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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-23. 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 |  Lodestar Stamp |  LayerOne (DocX + Sign) |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.19 Downloads/month (npm): 2 057 Downloads/week (npm): 722 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (npm): 116 Downloads/week (npm): 12 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.1.19 Downloads/month (npm): 2 057 Downloads/week (npm): 722 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
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 | Lodestar Stamp | LayerOne (DocX + Sign) |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-14 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (layerone-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 2 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/banjo-ventures/lodestar-stamp-mcp | github.com/golayerone/layerone-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | no remote endpoint we check |
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
Lodestar Stamp
Lodestar issues signed, dated business records. Reads are free.
LayerOne (DocX + Sign)
MCP server for LayerOne DocX (documents & Factur-X) and Sign (e-signature) APIs.
How to run each
Lodestar Stamp As a remote MCP server
claude mcp add --transport http lodestar-stamp https://api.lodestarindex.com/mcpLayerOne (DocX + Sign) As a local MCP server: npm package
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-mcpRequires: 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.
Only Lodestar Stamp has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of LayerOne (DocX + Sign) nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of Lodestar Stamp publish no settings it asks for, so we do not compare settings.
What it can do: Lodestar Stamp · What it can do: LayerOne (DocX + Sign) · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.