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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| marketplace_publishA | 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_searchA | Search the global marketplace for listings. filter by: kind (mcp_server|knowledge|idea), domain (crypto, reverse, algo, embedded, ...), tags, and free-text query. |
| marketplace_subscribeA | 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_pullA | 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_exportA | 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 covers a distinct marketplace operation: publish, search, subscribe, pull, outbox, export, and stats. There is no overlap between these actions, and an agent can easily choose the correct tool based on the desired operation.
All tools share the 'marketplace_' prefix, but the second part mixes verbs (publish, search, subscribe, pull, export) with nouns (outbox, stats). This is a minor deviation from a fully consistent verb_noun pattern, but the prefix ensures predictable grouping.
With 7 tools, the server is well-scoped for a marketplace-focused MCP. Each tool earns its place, and the count is within the ideal 3-15 range, avoiding bloat while covering the core operations.
The core marketplace lifecycle is covered: publish, search, subscribe, pull, outbox, export, and stats. Missing features include updating or unpublishing listings and unsubscribing, but these are minor gaps that do not block primary workflows.