_ registry / mcp streamable-http · checked 2h ago

DMCommerce

https://commerce.designmaster.com.br

Registry code: 0b36491ac24df25c

api record

Shop at Brazilian online stores that run on DMCommerce. Prices are in BRL and shipping is quoted to a Brazilian CEP.

Flow: search_products (or find_store first when the person names a store), then get_product for sizes, colors,

endpoint
https://commerce.designmaster.com.br/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is DMCommerce live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is DMCommerce free to use?
Yes — the hub reached it with no key and no payment.
What tools does DMCommerce have?
4 tools: search_products, get_product, quote_shipping, find_store.
Is DMCommerce 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
211ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

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.

  • find_store open 2h ago

    Find online stores in Brazil that sell on DMCommerce, by store name or by what they sell (e.g. "jeans", "suplementos", "acessórios 4x4"). Leave query empty to list every store. Returns up to 20 stores with their website and main categories.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "Store name or kind of product, e.g. \"Zé Marcos 4x4\", \"moda infantil\", \"óculos\". Empty lists all stores."
        }
      }
    }
    arguments 9 lines
  • search_products unknown never probed

    Search products for sale in DMCommerce stores (Brazil), across every store or in one store. Returns up to 10 products with price in BRL, whether it is in stock, the store and the product link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "What the person is looking for, in Portuguese works best, e.g. \"calça jeans\", \"whey\", \"snorkel\"."
        },
        "store": {
          "type": "string",
          "description": "Store id (\"store\" field from find_store) to search only that store."
        },
        "max_price": {
          "type": "number",
          "description": "Highest price in BRL (reais), e.g. 150."
        }
      }
    }
    arguments 20 lines
  • get_product unknown 2h ago

    Get one product of a DMCommerce store: description, every option (size, color...) with its price in BRL and whether it is available, and the link that opens that option on the store website.

    mcp-tool

    {
      "type": "object",
      "required": [
        "store",
        "product"
      ],
      "properties": {
        "store": {
          "type": "string",
          "description": "Store id (\"store\" field from find_store or search_products)."
        },
        "product": {
          "type": "string",
          "description": "Product id (\"product\" field from search_products)."
        }
      }
    }
    arguments 17 lines
  • quote_shipping unknown 2h ago

    Quote shipping for a product option to a Brazilian postal code (CEP), with the same options and prices the store checkout shows: carrier, price in BRL and delivery time in business days. Nothing is reserved or bought.

    mcp-tool

    {
      "type": "object",
      "required": [
        "store",
        "variant_id",
        "cep"
      ],
      "properties": {
        "cep": {
          "type": "string",
          "description": "Brazilian postal code (CEP) of the delivery address, e.g. \"29102-010\"."
        },
        "store": {
          "type": "string",
          "description": "Store id (\"store\" field)."
        },
        "quantity": {
          "type": "integer",
          "description": "How many units. Defaults to 1."
        },
        "variant_id": {
          "type": "integer",
          "description": "The variant_id of the chosen option, from get_product."
        }
      }
    }
    arguments 26 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0b36491ac24df25c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0b36491ac24df25c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0b36491ac24df25c/badge.svg)](https://brick.blue/agent/0b36491ac24df25c?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.

_ how we know
card completeness
80%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.