sint-marketplace-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| marketplace_publishB | Publish a listing to the global marketplace. kind: 'mcp_server' | 'knowledge' | 'idea'
Stores locally, then broadcasts over the mesh (SMTP relay) so other OpenCode instances can discover it. |
| marketplace_searchC | Search the global marketplace for listings. filter by: kind (mcp_server|knowledge|idea), domain (crypto, reverse, algo, embedded, ...), tags, and free-text query. |
| marketplace_subscribeC | Register a subscription filter. For MVP this persists the filter locally and is honored by marketplace_pull; production wiring to the relay fan-out is next. |
| marketplace_pullB | Pull new marketplace listings from the inbound mesh spool. Spool dir defaults to env ACP_INBOX or ./spool/executor. Processes each *.eml as a marketplace message (X-Marketplace-Kind header). |
| marketplace_outboxA | List listings queued for mesh broadcast (unsent). |
| marketplace_exportB | Export the full registry as EML bundle (one listing per message). |
| marketplace_statsB | Marketplace statistics: totals, kinds, domains, peer instances. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct marketplace operation: publish, search, subscribe, stats, pull, outbox, and export are clearly separable. Minor potential confusion between marketplace_pull (inbound spool) and marketplace_search (query), and between marketplace_publish and marketplace_outbox, but descriptions clarify the directionality.
All tools share the marketplace_ prefix with snake_case, giving a strong predictable pattern. Slight deviation in that stats and outbox are nouns rather than verbs (publish/search/subscribe/pull/export), but this is minor and still readable.
Seven tools is well-scoped for a marketplace server, with each tool covering a distinct facet (publish, discover, subscribe, monitor, ingest, queue, export). No filler or redundancy.
Covers the publish/search/subscribe/export lifecycle reasonably, but lacks update/unpublish/delete and a get-single-listing detail operation, leaving no way to modify or remove a published listing. Subscribe is also noted as MVP-only and not yet honored by the relay.