Marketplace

Browse published tools

This page reads the live catalog from GET /v1/tools — prices as integer micro-USD strings, never as JSON numbers.

—catalog unreachable

This page could not read GET /v1/tools, so it cannot say what is published. This is a failed read, not an empty catalog — the two are different answers and this page keeps them apart.

What exists today

The creator side is built; no gateway is hosted

Creator onboarding

Creator onboarding, handle claims and publishing are implemented. A creator signs up, claims a handle, and publishes a tool version pointing at their own HTTPS endpoint.

The published catalogue

The catalogue is served from GET /v1/tools, and one tool's schema and example from GET /v1/tools/{name}. Prices come back as integer micro-USD strings, never as numbers.

Immutable versions

A published version is immutable: changing a price or an endpoint means publishing a new version, and callers upgrade deliberately.

Routing names

How a tool is addressed

The routing name shape and the rule that a version's price is immutable are real and implemented.

Routing nameshape

<creator-handle>/<mcp-name>[@v<version>]/<tool-name>

creator-handle/mcp-name/tool          latest PUBLISHED version
creator-handle/mcp-name@v2/tool       pinned to version 2

Segments
Segment	Meaning
creator-handle	The handle the creator claimed. It is where the creator's revenue accrues.
mcp-name	The MCP server the creator published.
@v<version>	Optional. Pins one published version; without it, the name resolves to the latest published version. Every listed name is callable without pinning.
tool-name	The tool inside that MCP server.