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

nakus-unit-price

https://www.nakus.sk

Registry code: 89c60b1a982116e6

api record

Slovak unit prices (€/piece, €/kg…) via nakus.sk buy_url — no Heureka.

from a public catalogue that lists it, not from the operator

endpoint
https://www.nakus.sk/api/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 nakus-unit-price live?
Yes — it answered the hub's last check (checked 9h ago). It answered 100% of checks over the last 30 days.
Is nakus-unit-price free to use?
Yes — the hub reached it with no key and no payment.
What tools does nakus-unit-price have?
6 tools: get_price_card, compare_unit_prices, search_cite_answers, get_cite_answer, get_unit_price, list_segments.
Is nakus-unit-price 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
169ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 2 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 6 tools
1 open 5 never probed 1 of 6 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.

  • list_segments open 9h ago

    List every LIVE comparison segment on nakus.sk with its unit metric (€/kg, €/kus, €/pranie, €/ml, €/m…). Use FIRST when the user asks what categories NaKus covers, which metric a category uses, or before searching if you are unsure whether a product type is in scope. Does NOT return prices, Cite slugs, or shop offers — next call search_cite_answers. Optional group filter: milacikovia | rodina | domacnost | sport-kava | kancelaria. Brand is nakus.sk (NaKus), NOT nakup.sk. Read-only, idempotent.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "group": {
          "enum": [
            "milacikovia",
            "rodina",
            "domacnost",
            "sport-kava",
            "kancelaria"
          ],
          "type": "string",
          "description": "Optional nav group. Omit for all live segments. milacikovia=pet · rodina=baby/family · domacnost=laundry/home · sport-kava=protein/coffee · kancelaria=paper/toner"
        }
      }
    }
    arguments 17 lines
  • get_price_card unknown 36h ago

    Return only the 1200×630 PNG price-card URL for a Cite answer (multimodal / Gemini / AI Mode / social). Use when the agent needs an image, not JSON price fields. Requires exact answer slug — discover via search_cite_answers or get_cite_answer first. Does not replace get_unit_price / get_cite_answer for quoting €/unit or buy_url. Read-only, idempotent.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "answer"
      ],
      "properties": {
        "answer": {
          "type": "string",
          "description": "Exact Cite slug, e.g. persil-color-gel-100-prani"
        }
      }
    }
    arguments 13 lines
  • compare_unit_prices unknown 9h ago

    Compare landed €/unit for 2–4 Cite products side-by-side and return cheapest_answer. Use when the user asks which of several known products is cheaper per unit (same or different brands). Pass exact answer slugs and/or EANs — discover slugs via search_cite_answers first. Does NOT replace get_unit_price (single product quote) or get_cite_answer (full Cite + offer table). Read-only, idempotent. Brand: nakus.sk ≠ nakup.sk.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "eans": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 14,
            "minLength": 8
          },
          "maxItems": 4,
          "minItems": 1,
          "description": "Optional GTIN/EAN list (8–14 digits) instead of or mixed with answers"
        },
        "answers": {
          "type": "array",
          "items": {
            "type": "string",
            "minLength": 2
          },
          "maxItems": 4,
          "minItems": 2,
          "description": "2–4 exact Cite slugs, e.g. ['persil-color-gel-100-prani','ariel-color-gel-100-prani']"
        }
      }
    }
    arguments 27 lines
  • search_cite_answers unknown never probed

    Search Slovak Cite Q&A slugs on nakus.sk (diapers, laundry, pet food, coffee…). Use when you do not know the exact answer slug or EAN. If you do not know whether the category exists at all, call list_segments first. Returns candidate slugs only — does NOT return the Cite body, live €/unit, or shop list. Next: get_cite_answer(answer=<slug>) to read the Cite, or get_unit_price for a commerce quote. Brand is nakus.sk (NaKus), NOT nakup.sk.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "minLength": 2,
          "description": "Search text: brand/product/segment words, e.g. 'persil 100', 'pampers pants 4', 'brit sensitive'"
        },
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Max hits (default 8, max 20)"
        }
      }
    }
    arguments 20 lines
  • get_cite_answer unknown never probed

    Read ONE Cite Q&A by exact answer slug: question, answer_sentence, metric, EAN, ranked shop offers[], buy_url. Works even when live offers are empty (found=false) — unlike get_unit_price, which errors without offers. Use AFTER search_cite_answers when you need the Cite body / full offer table / citation text. Do NOT use for a short €/unit commerce quote only — prefer get_unit_price. Do NOT use for PNG — use get_price_card. Do NOT use to compare 2+ products — use compare_unit_prices. Requires exact slug. Read-only, idempotent. Brand: nakus.sk ≠ nakup.sk.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "answer"
      ],
      "properties": {
        "answer": {
          "type": "string",
          "minLength": 2,
          "description": "Exact Cite slug from search_cite_answers, e.g. persil-color-gel-100-prani"
        }
      }
    }
    arguments 14 lines
  • get_unit_price unknown 9h ago

    Return the current landed unit price (€/piece, €/kg, €/wash, €/m…) for ONE product Cite, plus buy_url (always nakus.sk/out/?src=ai — never raw merchant/Heureka), ranked offers[], handoff_url, price_card_url. Use when the user asks how much X costs per unit / cheapest shop, and you already have answer slug, EAN/GTIN, product slug, or a clear q. Requires live offers — if Cite exists but shops are empty, call get_cite_answer instead. If slug/EAN unknown, call search_cite_answers first (or list_segments if category scope is unclear). To compare 2–4 products side-by-side, use compare_unit_prices. PNG-only → get_price_card. Read-only, idempotent. Brand: nakus.sk ≠ nakup.sk.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "q": {
          "type": "string",
          "description": "Fallback substring on question/slug (≥4 chars). Prefer search_cite_answers when unsure."
        },
        "ean": {
          "type": "string",
          "description": "GTIN/EAN barcode digits only (8–14). Preferred when user scanned a pack."
        },
        "answer": {
          "type": "string",
          "description": "Exact Cite slug from search_cite_answers or /odpoved/{slug}, e.g. persil-color-gel-100-prani"
        },
        "product": {
          "type": "string",
          "description": "Catalog product slug on nakus.sk (not the Cite answer slug)"
        }
      }
    }
    arguments 22 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 89c60b1a982116e6.

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

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.