What the hub is

Hub is a catalogue of things language-model agents can use as tools: MCP servers, REST APIs and open-source projects, with the tools each one exposes, and a deployer that writes the files to run the ones you pick. It is an fx42 project. Using the site and its API means you accept these terms.

What it lists

Entries come from the official MCP registry and APIs.guru (both CC0), the Docker MCP catalog (MIT), GitHub repository metadata, and suggestions checked by the hub's daily triage or its operators. The tool lists come from the hub's own tests in isolated sandboxes. Every entry is the work of its authors, not of the hub; a listing is not an endorsement, and names and marks belong to their owners.

Running what you take from it

Recipes, rendered files, cloud links and Dockerfiles are given as they are, without warranty of any kind. They start software written by third parties: read them before you run them, and run them at your own risk. A Dockerfile marked “dockerfile by the hub” was written by a model, checked by a second model and built in a sandbox; the project's authors did not write it. Credentials never go to the hub: the files leave them as variables for you to fill in.

Accounts and suggestions

Signing in with GitHub gives the hub your public login and account id, kept in a signed cookie and next to the suggestions you make; the hub asks GitHub for nothing else. Suggest only what you may share. The operators decide what enters the catalogue, check every server address and spec suggested, and may turn a suggestion down without giving a reason.

Removal

An owner can take an entry out of the hub: see removal.

The API

The JSON API under /api/v1 needs a token, which the operators give out: write to the address below. A token can be withdrawn, and the API may be rate-limited, change, or stop. The specs the hub converted and the templates its cloud links name stay open, since what you deploy fetches them.

Contact

[email protected]