Ecommerce Prompts
Registry code: 96fe9fc21e667946
Free copy-and-run ChatGPT prompts for online stores: 924 prompts, 43 categories + 10 tasks.
from a public catalogue that lists it, not from the operator
- endpoint
- https://prompts-mcp.xpay.sh/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is Ecommerce Prompts live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
- Is Ecommerce Prompts free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does Ecommerce Prompts have?
- 4 tools: get_collection_prompts, search_prompts, get_prompt, list_collections.
- Is Ecommerce Prompts safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.5%· all time 99.5%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- ai & agents
- used for
- search ecommerce chatgpt prompts
- get prompts in a collection
- get a prompt template
- takes → gives
- text → text
- tools
- 4 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_collections reads open 16h ago
List every prompt collection in the free ecommerce ChatGPT prompt library at xpay.sh/prompts — 43 store-type categories (skincare, coffee, apparel, …) and 10 marketing-task sets (email, SEO, product descriptions, ads, …). Returns each collection's slug, label, kind, prompt count, and page URL.
{ "type": "object", "properties": { "kind": { "enum": [ "category", "task" ], "type": "string", "description": "Filter to store-type categories or marketing tasks. Omit for all." } } }arguments 13 linesget_collection_prompts reads unknown 16h ago
Get all copy-and-run ChatGPT prompts in one collection (e.g. slug "skincare" or "email-marketing"). Each prompt includes the full fill-in-the-blank template body, its variables, the recommended AI model, and the source page URL on xpay.sh/prompts.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Collection slug from list_collections, e.g. \"coffee\" or \"seo\"." } } }arguments 12 linessearch_prompts reads unknown 16h ago
Search the whole ecommerce prompt library by keyword (matches prompt title, summary, body, and collection). Returns matching prompts with their collection and source URL. Use to find prompts for a specific store type or marketing job.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "number", "description": "Max results (default 15, max 50)." }, "query": { "type": "string", "description": "Keywords, e.g. \"abandoned cart email\" or \"product description for candles\"." } } }arguments 16 linesget_prompt reads unknown 12h ago
Get one prompt by its id, with the full template body, variables, recommended model, pro tip, and source URL.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Prompt id from search_prompts or get_collection_prompts." } } }arguments 12 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id96fe9fc21e667946.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/96fe9fc21e667946/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/96fe9fc21e667946?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.