_ registry / mcp streamable-http · checked 10m ago

dinilu-dinilu.dk-da

https://dinilu.dk

Registry code: e3bfa94254f4c471

api record

Dinilu Tryk+Promo — B2B custom-printed promotional products.

This endpoint is bound to ONE domain and language: dinilu.dk, language "da", prices in DKK, sold from Netherlands.

endpoint
https://dinilu.dk/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 dinilu-dinilu.dk-da live?
Yes — it answered the hub's last check (checked 10m ago). It answered 100% of checks over the last 30 days.
Is dinilu-dinilu.dk-da free to use?
Yes — the hub reached it with no key and no payment.
What tools does dinilu-dinilu.dk-da have?
5 tools: fetch, get_product, get_quote, search_products, search.
Is dinilu-dinilu.dk-da 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
132ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 499 checks · signed record
  • down → live
_ what it is for
used for
  • search custom printed promotional products
  • get product options
  • get a price quote with shipping
takes → gives
text, data → data
tools
5 reads
_ 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 5 tools
2 open 3 never probed 2 of 5 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.

  • search_products reads open 23h ago

    Find products in this catalogue by free text and/or category. Returns mpn, title, page URL and category for each match. The mpn is what get_product and get_quote take.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Maximum results to return. Default 50, maximum 200."
        },
        "query": {
          "type": "string",
          "description": "Free text matched against the product title, case-insensitive. Omit to list everything (optionally narrowed by category)."
        },
        "category": {
          "type": "integer",
          "description": "Taxonomy term id to filter by. Read the category tree from the dinilu://categories resource."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • search reads open 16h ago

    Compatibility search for research clients that require a tool named "search". Returns only id, title and URL. Prefer search_products, which also filters by category and returns the category of each hit.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Free text matched against the product title."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • fetch reads unknown 23h ago

    Compatibility fetch for research clients that require a tool named "fetch". Returns one product as readable text. It carries NO price: prices depend on quantity and options and come from get_quote.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The id returned by search (the product mpn, as a string)."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_product reads unknown 23h ago

    Get a product's configurable attributes and their options, plus its minimum order quantity and quantity step. Call this before get_quote: the attribute and option ids it returns are what get_quote expects.

    mcp-tool

    {
      "type": "object",
      "required": [
        "mpn"
      ],
      "properties": {
        "mpn": {
          "type": "integer",
          "description": "Product MPN, from search_products or from the mpn field in a product page's JSON-LD."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_quote reads unknown 16h ago

    Price a specific configuration and quantity, with production time and shipping options. Indicative, excludes VAT and shipping, never binding. Read the returned "warnings" before presenting the price.

    mcp-tool

    {
      "type": "object",
      "required": [
        "mpn"
      ],
      "properties": {
        "mpn": {
          "type": "integer",
          "description": "Product MPN."
        },
        "qty": {
          "type": "integer",
          "description": "Quantity in PIECES. Below the product minimum it is raised to the MOQ and a qty_below_minimum warning is returned. Omitting it quotes the product default and warns — always pass the real target quantity, because price per piece changes substantially with volume."
        },
        "zone": {
          "type": "integer",
          "description": "Optional zone/state id, where shipping rates depend on it."
        },
        "country": {
          "type": "string",
          "description": "Destination country for shipping rates. Accepts a name (\"Germany\"), ISO 3166-1 alpha-2 (\"DE\"), alpha-3 (\"DEU\") or numeric (\"276\"). Defaults to this domain's country."
        },
        "attributes": {
          "type": "object",
          "description": "Option selection as {\"<attribute id>\": <option id>}, e.g. {\"19\": 251, \"58\": 490}. Both ids come from get_product. Option NAMES are also accepted as values but must match exactly, including double spaces, and are translated per domain — prefer ids. Any attribute you omit is filled with the product default and reported in warnings.",
          "additionalProperties": {
            "type": [
              "integer",
              "string"
            ]
          }
        }
      },
      "additionalProperties": false
    }
    arguments 35 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 e3bfa94254f4c471.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e3bfa94254f4c471/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/e3bfa94254f4c471/badge.svg)](https://brick.blue/agent/e3bfa94254f4c471?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
90%

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.