Comparison

API Gateway vs Vibenate

API Gateway is an MCP server published by rflpazini. Marketplaces we read that list it: 1 (Docker MCP Catalog). Vibenate is an MCP server published by vibenate.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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

Where each is published
Marketplace	API Gateway	Vibenate
Docker MCP Catalog	Listed Version: sha256:9cc67b4a037f Forks (GitHub): 12 Pulls (Docker Hub): 59 566 Stars (Docker Hub): 6 Stars (GitHub): 44 Not marked · First seen 2026-10-11	Not listed
Official MCP Registry	Not listed	Listed Version: 2.8.4 No figure published Not marked · First seen 2026-10-13

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

API Gateway vs Vibenate
Fact	API Gateway	Vibenate
Marketplaces that list it	1	1
Stars (GitHub) (differs)	44	No figure on GitHub
Pulls (Docker Hub) (differs)	59 566	No figure on Docker Hub
Forks (GitHub) (differs)	12	No figure on GitHub
Last release (differs)	Not published	2026-10-13
Where it runs (differs)	On your machine (mcp/api-gateway)	Remote server (vibenate.com/mcp)
Transport (differs)	stdio	Streamable HTTP
Tools it declares (differs)	2	Not published
Environment variables it asks for (differs)	3, secrets among them: 0	Not published
Licence	Not stated	Not stated
Repository (differs)	github.com/rflpazini/mcp-api-gateway	Not stated
Changes in the last 7 days	0	0
First seen (differs)	2026-10-11	2026-10-13
Endpoint at the last check (differs)	no remote endpoint we check	Responded 3 days ago

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

API Gateway

In its own words, on Docker MCP Catalog:

A universal MCP (Model Context Protocol) server to integrate any API with Claude Desktop using only Docker configurations.

Vibenate

In its own words, on Official MCP Registry:

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

How to run each

API Gateway As a local MCP server: Docker image

Claude Code

claude mcp add --transport stdio mcp-api-gateway -- docker run -i --rm mcp/api-gateway

Vibenate As a remote MCP server

Claude Code

claude mcp add --transport http vibenate https://vibenate.com/mcp

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

Only Vibenate has a remote endpoint we check. How we check endpoints

Tools each declares

Only API Gateway has

execute_api
get_api_info

Only Vibenate has

apply_correction
attach_evidence
browse_catalogue
check_connection
check_contribution_connection
compare_services
create_publisher_claim
draft_submission
edit_comment
filter_sites
get_agent_brief
get_agent_path

Show the remaining 46

get_agent_profile
get_corrections
get_dependency_changes
get_discussion
get_filtered_changes
get_job_status
get_my_contributions
get_my_identity
get_observation_history
get_operational_outcomes
get_participation_guide
get_participation_inbox
get_participation_policy
get_path_history
get_reason_codes
get_registry_statistics
get_submission_status
get_watchlist
get_work_queue
import_contribution_packet
inspect_documentation
inspect_site
preflight_submission
publish_declaration
read_documentation
reconcile_mutation
record_decision
record_observation
report_problem
request_documentation_refresh
resolve_correction
resolve_question
resolve_task
retract_comment
retract_review
retract_vote
search_sites
set_vote
submit_service
suggest_correction
unwatch_dependency
validate_submission
verify_publisher_claim
watch_dependency
write_comment
write_review

Both have

None

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

Settings each asks for

The marketplaces of Vibenate publish no settings it asks for, so we do not compare settings.

What it can do: API Gateway · What it can do: Vibenate · 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-28. We publish no contact details for plugin publishers.