ucie-wrap vs Glif
ucie-wrap is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
ucie-wrap is a plugin bundle for AI coding tools published by andrewb1999. 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-22. 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 andrewb1999/ucie-wrap-plugin | Removed on 2026-10-15 Version: 0.2.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): 32 Stars (GitHub): 215 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:3f93ddceeb99 Forks (GitHub): 32 Pulls (Docker Hub): 19 777 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 | ucie-wrapno 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 777 |
| Forks (GitHub) (differs) | 0 | 32 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | 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) | 1 | 11 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/andrewb1999/ucie-wrap-plugin | github.com/glifxyz/glif-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 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 ucie-wrap
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
High-level synthesis — C/C++ to RTL, directive optimization, co-simulation
-
An AI coding skill (Claude Code / Codex / OpenClaw) that turns natural language into production-ready Vivado / Vitis HLS / Vitis Unified / PetaLinux scripts. Describe what you…
-
Native MCP server for controlling AMD/Xilinx Vivado on Windows and Linux via persistent Tcl.
-
AI-assisted IC design flow skills — specification, RTL, lint/CDC, simulation, synthesis, timing analysis, and signoff
-
EDA tool detection, output-filtering shell wrappers, MCP server config templates, and memory distillation for all chip-design domain agents
-
Logic synthesis — SDC constraints, compile optimization, netlist QC and LEC
What each says it does
ucie-wrap
Wrap Vitis HLS AXIS kernels with a verified UCIe FDI die-to-die interface
Glif
Generate images, video, and audio with Glif's media-generation agent
How to run each
ucie-wrap
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 ucie-wrap publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of ucie-wrap publish no settings it asks for, so we do not compare settings.
What it can do: ucie-wrap · 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.