MCP Marketplace · earlier pilot specification
Scope superseded: see the public shared-MCP release specification. Private deployment and operator-script flows below describe earlier pilot behavior; dedicated customer infrastructure is deferred. Historical verification evidence is retained.
A visitor can find an MCP server by the job it performs, inspect a sample and decide how to connect it. A team member can deploy a private instance on a trusted Docker host and give its endpoint to an MCP client. The marketplace, HTTP API and MCP interface are the phase-one product. The graphical workflow editor is a later phase.
Decision status. The owner requested a dark, glass streaming-library layout and supplied a working visual reference. The flows and acceptance thresholds below are the proposed product contract. Independent walkthrough results are recorded separately below. No user-study results are available.
What the shopper can do
| Starting point | Shortest intended path | Observable result |
|---|---|---|
| New visitor, public catalog | Select Explore Text stats on the featured banner. | One activation opens the actual service details, including its word-count example, setup and access requirements. |
| Analyst with a tool name | Search for word_count. Open Text stats. |
The matching product explains the input, output, tool name and access. Search reacts to typing, with one activation to open a result. |
| Engineer looking for storage | Search for S3. Open the matching integration. |
The detail shows read-only access, required configuration and stdio connection instructions. A separately provisioned integration leads to setup. |
| Member on managed HTTPS | Select a built-in profile from its listing. Review the private default and deploy. Copy the endpoint. | A real instance appears in the member's list. Its URL can be used with a separate bearer credential. After authentication, target three activations from the listing. |
| Package author | Open the upload form in the workspace, choose Python or OCI and send the file for review. | The member sees the package name, immutable digest and review status. It becomes deployable only after an operator approves the exact package and tool schemas. |
| Operator | Inspect pending original bytes and schemas. Approve a package or leave it pending. Inspect active replicas and remove an instance when finished. | Approval and deployment are distinct events. Removing an instance releases its capacity. The managed API exposes the same state. |
An activation is a click, tap or keyboard activation of a control. Text entry and authentication are counted separately. A copied configuration must describe a real connection available in the current mode. Public examples are labeled as sample requests. A managed tool call reports the response received from its instance.
Catalog, workspace and documentation
The marketplace opens with one featured task. Search follows it immediately. The two built-in profiles are Text stats and Text cleaning. Thematic shelves organize the catalog into Data, Social, LLMs, Transcription, Search and Developer tools. Telegram archive extraction belongs to Social. Daedro Voice and Daedro Video process separately uploaded media through their own services. A product tile shows its name, a useful outcome and whether it runs on this Hub or is provisioned separately. A product detail discloses tools, authorization requirements, an example and the next executable action. Protocol and service ID remain searchable.
The public catalog works without configuration or Docker. Without a configured workspace, its featured action opens the Text stats listing. If the operator supplies a local managed HTTPS port, Use Text stats opens that separate workspace with the correct profile selected. The destination requires its own trusted certificate and bearer token. On an unlinked catalog, the workspace explains managed setup and links directly to the corresponding guide section. When the Hub is running with managed HTTPS, the same listing selects the correct profile. Credentials are entered in the managed workspace. Private is selected before deployment. Shared instances are available to authenticated Hub members. A copyable endpoint contains no secret. A signed-out visitor can still browse.
The developer guide at /docs serves SDK examples, S3 setup, package review, private and shared access, budgets and troubleshooting. The running OpenAPI document describes that caller's HTTP operations and MCP tools. Public and protected capability lists can differ. Operator guide · Trust boundary
Interaction to verify before release
- From a clean public session, choose Explore Text stats. Identify the tool, the text it accepts, the output it promises and where to run it. Its sample request is visible without signing in.
- Find S3 by name. Identify the credential owner, how it connects and who provisions it. The path must lead to the correct setup.
- In a fresh authenticated session, select Text stats, deploy it privately and copy the endpoint. Run “Quarterly revenue increased.” and verify that the real endpoint returns 3. A second caller must be denied. On an explicitly shared instance, the second caller can invoke the tool.
- Search for a nonsense term. Clear the search and recover the shelf. Close a detail and return to its triggering tile with focus and query intact.
- On a narrow viewport and with keyboard-only input, reach search, open a tile and read its setup instructions. The bottom dock must leave the final button and focused item visible.
Error messages name the affected task and its recoverable next step. Text remains available after a rejected request. The UI differentiates an invalid credential, an unavailable worker, an exhausted budget and an unapproved upload. Repeated activation during an active deployment must not create a second instance.
Verification record
Previous home. An independent Chrome walkthrough at 1522 × 882 found ten entries. The API endpoint table and management setup preceded search. Only two complete service rows were visible initially. Entering word_count produced one match. Opening Text stats revealed a correct input, output and copyable JSON example. The public card had no runnable sample. A visitor could open the operator guide from an earlier section.
Revised public marketplace. The independent Chrome walkthrough counted 13 services across six themes (Data 5, Social 1, LLMs 1, Transcription 2, Search 2 and Developer tools 2). Explore Text stats opened its real setup, access conditions, tool and sample request in one activation. Search for word_count returned one listing. The Social chip returned the Telegram archive service. Transcription returned the separate audio and video services. Searching for S3 surfaced the adapter and a Hub API listing that references S3. Opening the adapter with Enter exposed its stdio launcher, credential scope and five read tools. In public mode, both Workspace and Upload displayed the managed setup link. Docs opened the live API and MCP reference. In the corrected build, selecting Social after opening Text stats and activating the same featured link again restored its visible detail. Clear filters restored all 13 results from an empty search with Enter. On the separately configured catalog, the featured action linked to the local HTTPS workspace and selected the Text stats profile without including a credential in the URL.
Narrow screen. With a measured 354 × 767 CSS-pixel viewport, the marketplace displayed one cover per row. The catalog and guide both fit the horizontal viewport. The Developer tools chip, initially outside the visible part of the scrollable row, could be reached and activated by keyboard. The bottom dock exposed all four labeled destinations.
Backend acceptance. The standalone HTTPS package smoke exercised Python and OCI packages, two private calls, four shared calls, denial of another member's private access, and a byte-identical operator review download. The real Docker lifecycle and race tests exercised restoration and quotas. These checks use synthetic requests on the local Docker host. Upload smoke · Managed smoke
For usability validation, give the same task and initial state to people unfamiliar with this Hub. Record how many attempted it, how many finished without intervention, where assistance was needed and whether each person understood where their text ran. Report partial completions alongside successes. Marketplace design