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

barcodereport

https://barcodereport.com

Registry code: 894d8de06182952a

api record

Barcode Report looks up products by barcode (UPC, EAN, GTIN or ISBN) across 500M+ records. Use lookup_barcode for one code, lookup_barcodes for several (up to 100 in one call), and search_products when you only have a product name. Each code looked up uses one lookup from the user's monthly allowance, including codes that are not found; a search uses one per call; get_usage is free. Every record has a title; brand, category, images and other fields are present on a smaller share. When a result includes an attribution string, show it with the data.

endpoint
https://barcodereport.com/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 barcodereport live?
Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
Is barcodereport free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does barcodereport have?
4 tools: get_usage, lookup_barcode, lookup_barcodes, search_products.
Is barcodereport 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 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
4 auth-required 4 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.

  • get_usage auth-required 8h ago

    Show the account's plan, monthly allowance, lookups used and when usage resets. Free.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • lookup_barcode auth-required 8h ago

    Find the product for one barcode: UPC-A, UPC-E, EAN-13, EAN-8, GTIN-14, ISBN-10 or ISBN-13. Returns the title and, where known, brand, category, description, image, price, identifiers and book details. Uses one lookup from the monthly allowance, even when the code is not found.

    mcp-tool

    {
  "type": "object",
  "required": [
    "barcode"
  ],
  "properties": {
    "barcode": {
      "type": "string",
      "maxLength": 32,
      "description": "The barcode, for example 049000050103. Spaces and dashes are ignored."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • lookup_barcodes auth-required 8h ago

    Find the products for up to 100 barcodes in one call. Duplicates are ignored. Uses one lookup per distinct code; if the batch would exceed the remaining allowance, nothing is looked up or charged.

    mcp-tool

    {
  "type": "object",
  "required": [
    "barcodes"
  ],
  "properties": {
    "barcodes": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 32
      },
      "maxItems": 100,
      "minItems": 1,
      "description": "Barcodes to look up."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • search_products auth-required never probed

    Search products by title, brand or category when you have a name rather than a barcode. Returns barcode, title, brand, category and image for the best matches. Words shorter than 3 letters are ignored. Uses one lookup per call.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "default": 1,
      "maximum": 100,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 120,
      "description": "Search text, for example \"nutella 400g\"."
    },
    "per_page": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    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 894d8de06182952a.

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