API.market MCP Gateway vs Janusmcp
A side-by-side look at the API.market MCP Gateway and Janusmcp MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
API.market MCP GatewayAggregators · Remote HTTP/SSEProprietary hosted Streamable HTTP MCP gateway for API discovery, operation schemas, API calls, usage checks and subscription management through five tools: search_apis, get_api_tools, call_api, check_usage and manage_subscription. Requires an API.market account with OAuth (recommended) or API-key authentication. Free tiers, paid plans and limits vary by API; API calls and subscription changes may incur charges. OAuth/PKCE and five-tool discovery verified with Claude Code 2.1.281; not every API operation or client has been tested. The public integration repository contains configuration and documentation, not the hosted server implementation. Connect directly to https://api.market/api/mcp/gateway; no local package is required.52GoodAuth: oauth 2.0Verdict: choose API.market MCP Gateway for aggregators work over a hosted endpoint; choose Janusmcp for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose API.market MCP Gateway when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Choose Janusmcp when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A API.market MCP Gateway | |
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 52/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 9 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View API.market MCP Gateway | View Janusmcp |
Tools & capabilities
API.market MCP Gateway tools
No tool names declared yet. Check the project README from the listing page.
Janusmcp tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
API.market MCP Gateway
{
"mcpServers": {
"api-market-mcp-gateway": {
"url": "https://api.market/api/mcp/gateway"
}
}
}
Janusmcp
{
"mcpServers": {
"janusmcp": {
"command": "npx",
"args": [
"-y",
"@bayway/janusmcp"
]
}
}
}
Frequently asked questions
API.market MCP Gateway is categorized under Aggregators and uses a remote HTTP/SSE transport. Janusmcp belongs to Aggregators and uses a local stdio subprocess. Pick API.market MCP Gateway for aggregators work and Janusmcp for aggregators.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
API.market MCP Gateway is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. Janusmcp has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add api-market-mcp-gateway and janusmcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, API.market MCP Gateway has a quality signal of 52/100 (Good) with 3 views, 0 installs and 0 GitHub stars. Janusmcp has 47/100 (Fair) with 0 views, 0 installs and 9 GitHub stars.