Emboss vs Glif
Emboss is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
Emboss is a plugin bundle for AI coding tools published by Edwin Orange. No marketplace we read lists it any more. Glif is an MCP server published by glif.app. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Glif | |
|---|---|---|
| Community marketplace getemboss-ai/emboss-claude-plugin | Removed on 2026-10-15 Version: 1.7.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 36 Stars (GitHub): 215 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:3f93ddceeb99 Forks (GitHub): 36 Pulls (Docker Hub): 19 761 Stars (Docker Hub): 2 Stars (GitHub): 215 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 | Embossno longer listed · | Glif |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 3 |
| Stars (GitHub) (differs) | 0 | 215 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 19 761 |
| Forks (GitHub) (differs) | 0 | 36 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.getemboss.ai/mcp) | Remote server or your machine |
| Transport (differs) | Streamable HTTP | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 10 |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | 6 | 11 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/getemboss-ai/emboss-claude-plugin | github.com/glifxyz/glif-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Emboss
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Fill existing fillable, flat and scanned PDF forms from structured data; save reusable templates
-
Prepare and track US PDF faxes with user-approved checkout. No account or subscription.
-
AI-powered PDF tools: fill forms via natural language
-
Detect fillable fields in any PDF with AI, scans included, then fill and sign it.
-
Send a fax from Claude, ChatGPT, or Cursor. Upload a PDF, pay, get delivery status.
-
Send real faxes from AI chat (DE/AT + 40 countries). PDF, JPG, photo. Pay per fax via Stripe.
What each says it does
Emboss
Emboss turns any PDF form into a fillable one, fills it from data or supporting documents, reads a filled form back, and faxes the result to a US, Canadian or Mexican fax number.
Glif
Generate images, video, and audio with Glif's media-generation agent
How to run each
Emboss
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Glif As a remote MCP server
claude mcp add --transport http glif https://glif.app/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Glif has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Emboss publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Emboss publish no settings it asks for, so we do not compare settings.
What it can do: Emboss · What it can do: Glif · Compare two other plugins
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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.