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

com.mcpscores/food-facts

https://food-facts.bowling-anthony.workers.dev

Registry code: 8a0d204460780ea7

api record

Someone asked whether they can eat this and all you have is the barcode. Tool calls are x402-paid in USDC on Base: send the base64 X-PAYMENT header on this POST /mcp request (or params._meta['x402/payment']). food_by_barcode costs $0.005. initialize, ping and tools/list are free, as are request_data and demand_report. Data is Open Food Facts, crowd-sourced and openly licensed: coverage is uneven and records can be sparse, so check dataCompleteness and treat null as unknown rather than zero. An unknown barcode returns not_found and is NOT charged.

endpoint
https://food-facts.bowling-anthony.workers.dev/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 com.mcpscores/food-facts live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is com.mcpscores/food-facts free to use?
Not measured yet.
What tools does com.mcpscores/food-facts have?
3 tools: demand_report, request_data, food_by_barcode.
Is com.mcpscores/food-facts 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 99.6%· all time 99.6%

latency
152ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 484 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
lifestyle & home food & drink
used for
  • look up a packaged food by barcode
  • check ingredients and allergens
  • request data not yet offered
takes → gives
text → data
tools
2 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 12 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
15

distinct

settlements
39

last 2026-11-05

received on chain
0.228 USDC

shared-payto

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • demand_report reads unknown never probed

    FREE, no payment. The aggregate of what agents have told us they are looking for, most-requested first, with the categories nothing available yet serves.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "string",
      "examples": [
        "30"
      ],
      "description": "Window in days, default 30, max 90."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • request_data changes data unknown never probed

    FREE, no payment. Describe in your own words the data you are trying to buy — anything, not just food — and get back whether we operate a service that supplies it, with the MCP endpoint if so. Every request is catalogued so repeatedly-requested data gets built. Nothing identifying is stored, only the words of the request.

    mcp-tool

    {
  "type": "object",
  "required": [
    "need"
  ],
  "properties": {
    "need": {
      "type": "string",
      "examples": [
        "live electricity spot prices by ZIP"
      ],
      "description": "What you are looking for."
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • food_by_barcode reads unknown never probed

    Look up a packaged food by its barcode and get the fields that answer "can this person eat this?" — ingredients, allergens, traces, additives, Nutri-Score, NOVA processing group and per-100g nutrition. Data is from Open Food Facts, which is crowd-sourced and openly licensed: coverage is uneven by country and a product can be listed with most nutrition empty, so every response carries a completeness flag and missing values are null rather than estimated. A barcode not in the database returns not_found and is NOT charged. Costs $0.005 USDC per call via x402 on Base.

    mcp-tool

    {
  "type": "object",
  "required": [
    "barcode"
  ],
  "properties": {
    "barcode": {
      "type": "string",
      "examples": [
        "737628064502"
      ],
      "description": "6-14 digit product barcode, e.g. '737628064502'."
    }
  },
  "additionalProperties": false
}
    arguments 16 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 8a0d204460780ea7.

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

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.