Marketplace MCP server

Read from the package source without running it. The installed server may list more.

• marketplace_confirm_publishwrite action

  Execute a previously-prepared marketplace publish, identified by its one-time token. Only meaningful when NOSTR_REQUIRE_CONFIRM=true. Single-use token; the safety pipeline re-runs before signing. For Shopstr-modern tools (kind:30019/30402), the Shopstr cache POST hook is re-attached automatically.

• marketplace_create_or_update_productwrite action

  Create or update a NIP-15 product (kind:30018) within a stall. The `stall_id` must match an existing stall's `id`. The `id` is the product's parameterized-replaceable d-tag \u2014 republishing with the same id replaces it. `categories` are surfaced as `t` tags for discoverability. Runs the safety pipeline (read-only, signer, rate limit, optional confirm).

• marketplace_create_or_update_stallwrite action

  Create or update a NIP-15 marketplace stall (kind:30017). The `id` field is the parameterized-replaceable identifier \u2014 publishing with the same id replaces the prior stall on relays that honor replaceability. Shopstr is the canonical UI for these events. Runs the safety pipeline (read-only, signer, rate limit, optional confirm).

• marketplace_list_my_products

  Fetch + parse the current signer's NIP-15 products (kind:30018). Returns each product's event id, created_at, `d` tag, category `t` tags, and parsed JSON (name, description, price, currency, stall_id, etc.). Optionally filter by stall_id (applied client-side after fetch \u2014 NOSTR relays don't index the JSON content). Products with non-JSON or schema-invalid content are returned with `parsed: nu

• marketplace_list_my_stalls

  Fetch + parse the current signer's NIP-15 stalls (kind:30017). For each stall event found on the configured relays, returns the event id, created_at, `d` tag, and the parsed stall JSON (name, description, currency, shipping). Stalls that don't pass the NIP-15 schema are returned with `parsed: null` so you can see what's wrong.

• shopstr_create_or_update_productwrite action

  Create or update a Shopstr-compatible product as a NIP-99 Classified Listing (kind:30402). All product data lives in tags; `summary` is the event content. The `d` tag is the supplied `id` \u2014 republishing replaces the prior listing. After relay publish, POSTs to Shopstr's cache (SHOPSTR_CACHE_URL) so the storefront UI surfaces the product. Runs the safety pipeline (read-only, signer, rate limit

• shopstr_create_or_update_shopwrite action

  Create or update the seller's Shopstr shop profile (kind:30019). The `d` tag is the seller's pubkey hex \u2014 one shop per pubkey. After relay publish, POSTs the event to Shopstr's cache (SHOPSTR_CACHE_URL) so the storefront UI surfaces it. Runs the safety pipeline (read-only, signer, rate limit, optional confirm).

• Code scan2 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 104 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

71/100

higher than 43% of 2,174 E-commerce servers

Tools

7

the typical E-commerce server has 6

Tools that change things

71%

typical: 0%. Fewer write tools means less an agent can break

Downloads a week

83

more than 64% of 411 E-commerce servers with a package

Marketplace: common questions

Is Marketplace MCP server safe?

Mostly: it is graded B (71/100). Read the Marketplace safety report

How do I install Marketplace?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Marketplace need an API key?

Yes. The registry entry asks for NOSTR_NIP46_URI, NOSTR_PRIVATE_KEY.

Is Marketplace maintained?

The last commit was 142 days ago (2026-06-15). The latest release is v0.2.3.

What can I use instead of Marketplace?

Servers from other publishers that do the same job: Secondhand MCP server, Store Builder MCP server and Apify MCP server.

How does Marketplace compare with other E-commerce MCP servers?

safety score 71/100 (higher than 43% of 2,174 E-commerce servers); tools 7 (the typical E-commerce server has 6); tools that change things 71% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.