UCM (Universal Commerce Marketplace)
ucmaiLABSCO SUMMARY
The key travels in the URL, which is convenient and worth thinking about twice.
A query-parameter credential is the easiest possible setup — paste one string and you are connected — and it is also the credential most likely to end up in a log, a browser history or a screenshot of a config file. The platform's own documentation offers general API-key hygiene and nothing MCP-specific, so the handling is on you. Treat the whole URL as the secret and rotate it like one.
What it is
A marketplace where each published API gets its own MCP address. There is no single endpoint — you build the URL from the API's slug and your key.
What you get
Whatever the API you connected exposes. The catalogue is the product, so the tool surface is defined by the individual API rather than by the platform.
Requirements
An API key, passed in the URL's query string. Personal is free with 500 requests a day, Team is $7 per user per month with 2,000; individual APIs price separately, from free to consumption-based, with prepaid credits that auto top-up below $5.
Setup effort
Get your endpoint, then paste it — add your endpoint to your client with your key
USE CASES
01
Reaching one API without writing a client
Take the API's slug from the catalogue, add your key, and the agent has it — no SDK, no wrapper.
02
Keeping request spend bounded
Prepaid credits with auto top-up below $5 and a daily request cap per plan put a ceiling on a runaway loop.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- apiKey query parameter
INSTALLATION
Connect your client
Add your endpoint to your client with your key.
Server setup
ENDPOINT URL
https://sse.api-hub.org/<YOUR_API_SLUG>/sse?apiKey=<YOUR_API_KEY>Requirements
- apiKey query parameter
