API Gateway vs io.github.costkits/costkits-mcp
API Gateway is an MCP server published by rflpazini. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.costkits/costkits-mcp is an MCP server published by costkits. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
| Marketplace |   API Gateway |  io.github.costkits/costkits-mcp |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:9cc67b4a037f Forks (GitHub): 12 Pulls (Docker Hub): 59 273 Stars (Docker Hub): 6 Stars (GitHub): 44 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.0 Downloads/month (npm): 407 Downloads/week (npm): 271 Forks (GitHub): 0 Stars (GitHub): 0 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 | API Gateway | io.github.costkits/costkits-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 44 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 59 273 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcp/api-gateway) | Remote server (mcp.costkits.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 | github.com/costkits/costkits-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| 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
A universal MCP (Model Context Protocol) server to integrate any API with Claude Desktop using only Docker configurations.
io.github.costkits/costkits-mcp
Free hosted MCP server: US healthcare procedure cost estimates and provider pricing. No API key.
How to run each
API Gateway As a local MCP server: Docker image
claude mcp add --transport stdio mcp-api-gateway -- docker run -i --rm mcp/api-gatewayio.github.costkits/costkits-mcp As a remote MCP server
claude mcp add --transport http costkits-mcp https://mcp.costkits.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.costkits/costkits-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
Only API Gateway has
execute_apiget_api_info
Only io.github.costkits/costkits-mcp has
calculate_liabilitycheck_financial_assistancecompare_bill_amountdemo_estimateestimate_procedure_costfind_providersfull_estimateget_coverageget_procedure_detailsget_providerlist_carrierslist_procedures
Show the remaining 1
resolve_procedure
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.costkits/costkits-mcp as of 2026-10-22). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of io.github.costkits/costkits-mcp publish no settings it asks for, so we do not compare settings.
What it can do: API Gateway · What it can do: io.github.costkits/costkits-mcp · 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.