Comparison

VeyraX vs io.github.marcosnovo/lexvibe

VeyraX is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.

VeyraX is an MCP server published by VeyraX. No marketplace we read lists it any more. io.github.marcosnovo/lexvibe is an MCP server published by marcosnovo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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

Where each is published
Marketplace	VeyraX	io.github.marcosnovo/lexvibe
Docker MCP Catalog	Removed on 2026-10-26 Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 659 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen 2026-10-11	Not listed
Official MCP Registry	Not listed	Listed Version: 1.0.4 Downloads/month (npm): 273 Downloads/week (npm): 63 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen 2026-10-11

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

VeyraX vs io.github.marcosnovo/lexvibe
Fact	VeyraXno longer listed · 2026-10-26	io.github.marcosnovo/lexvibe
Marketplaces that list it (differs)	0	1
Stars (GitHub) (differs)	48	0
Pulls (Docker Hub) (differs)	18 659	No figure on Docker Hub
Forks (GitHub) (differs)	19	0
Last release (differs)	Not published	2026-10-18
Where it runs (differs)	On your machine (mcp/veyrax)	Remote server (golexvibe.com/api/mcp)
Transport (differs)	stdio	Streamable HTTP
Tools it declares (differs)	3	Not published
Environment variables it asks for (differs)	1, secrets among them: 1	5, secrets among them: 0
Licence	Not stated	Not stated
Repository (differs)	github.com/veyrax/veyrax-mcp	github.com/marcosnovo/lexvibe-mcp
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 33 h 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 VeyraX

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

Vibenate

Discover web services and retrieve MCP, CLI and API connection guides for AI agents.

by vibenate.com · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
Laudex

Find MCP servers, APIs, tools and skills by intent. Free key: POST /api/agents/register

by laudex.dev · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
vivesca io.github.terry-li-hm/vivesca

Opinionated MCP server — Pydantic output schemas, 7 domains, built to evolve.

by terry-li-hm · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
Speakeasy Platform MCP

Secure and manage MCP servers through the Speakeasy AI Control Plane from your agent.

by ai.speakeasy.com · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
Trigger.dev MCP by usefulapi

Debug background jobs — runs, traces, spans, schedules, queues and deployments.

by usefulapi.io · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
forai.tools — let your agent find the right tool

Lets your agent find the right MCP server, tool or service for a task, in one call. Ads labelled.

by forai.tools · MCP server

Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

VeyraX

In its own words, on Docker MCP Catalog:

VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.

io.github.marcosnovo/lexvibe

In its own words, on Official MCP Registry:

One-step legal compliance for vibe-coded apps: privacy, terms, cookie banner and EU AI Act check.

How to run each

VeyraX

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.marcosnovo/lexvibe As a remote MCP server

Claude Code

claude mcp add --transport http lexvibe https://golexvibe.com/api/mcp

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

Only io.github.marcosnovo/lexvibe has a remote endpoint we check. How we check endpoints

Tools each declares

Only VeyraX has

get_flow
get_tools
tool_call

Only io.github.marcosnovo/lexvibe has

applicable_frameworks
check_ai_act
check_store
check_website
claim_app
generate_policies
get_claim_status
get_install_snippet
list_frameworks
lookup_framework

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.marcosnovo/lexvibe as of 2026-10-22). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only VeyraX asks for

VEYRAX_API_KEY (secret)

Only io.github.marcosnovo/lexvibe asks for

LEXVIBE_API_URL
LEXVIBE_APP_ID
LEXVIBE_CDN_URL
LEXVIBE_EVENTS_URL
LEXVIBE_TELEMETRY

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

What it can do: VeyraX · What it can do: io.github.marcosnovo/lexvibe · 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 2026-10-26. We publish no contact details for plugin publishers.