VeyraX vs Conquer Fear
VeyraX is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑10.
VeyraX is an MCP server published by VeyraX. No marketplace we read lists it any more. Conquer Fear is an MCP server published by lifeisagame.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 | ||
|---|---|---|
| Docker MCP Catalog | Removed on 2026-11-10 Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 911 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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 | VeyraXno longer listed · | Conquer Fear |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 48 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 18 911 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/veyrax) | Remote server (api.lifeisagame.ai/mcp/conquer-fear) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/veyrax/veyrax-mcp | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 18 h ago, requires authentication |
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 VeyraX
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Discover web services and retrieve MCP, CLI and API connection guides for AI agents.
-
Find MCP servers, APIs, tools and skills by intent. Free key: POST /api/agents/register
-
Tool-using planning agent over MCP servers, built on the Vercel AI SDK.
-
Find the right AI tool or MCP connector for a task; sourced directory of real AI-built apps.
-
List workflows and variables; create sessions and list session documents in Gavel.
-
vivesca io.github.terry-li-hm/vivesca
Opinionated MCP server — Pydantic output schemas, 7 domains, built to evolve.
What each says it does
VeyraX
VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.
Conquer Fear
Fear ladders for your assistant: small exposure steps, logged attempts, real progress.
How to run each
VeyraX
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Conquer Fear As a remote MCP server
claude mcp add --transport http conquer-fear https://api.lifeisagame.ai/mcp/conquer-fear
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Conquer Fear has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Conquer Fear publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Conquer Fear publish no settings it asks for, so we do not compare settings.
What it can do: VeyraX · What it can do: Conquer Fear · 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.