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

bam-catalog

https://realbam.be

Registry code: 6b64191dc374f0c5

api record

Read-only access to the BAM Kaarsen (realbam.be) candle catalog. Start with browse_catalog for the facet tree or search_products for keyword/EAN search; get_product returns full details. All tools accept lang: en, nl or fr.

endpoint
https://realbam.be/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 bam-catalog live?
Yes — it answered the hub's last check (checked 13h ago). It answered 99% of checks over the last 30 days.
Is bam-catalog free to use?
Yes — the hub reached it with no key and no payment.
What tools does bam-catalog have?
4 tools: get_product, search_products, browse_catalog, list_products.
Is bam-catalog 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
98.7%

90 days 98.7%· all time 98.7%

latency
98ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 228 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
payments & commerce shopping & products
used for
  • browse a candle catalog
  • search candle products
  • get product price and stock
takes → gives
text → data
tools
4 reads
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 4 tools
2 open 2 never probed 2 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.

  • browse_catalog reads open 13h ago

    The catalog navigation tree: scents, product types and collections with their ids, for use with list_products.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "lang": {
      "enum": [
        "en",
        "nl",
        "fr"
      ],
      "type": "string",
      "description": "Language for names and descriptions (default en)"
    }
  }
}
    arguments 14 lines
  • list_products reads open 13h ago

    List catalog products, optionally filtered by exactly one facet id from browse_catalog. Without a filter, returns the whole visible catalog.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "lang": {
      "enum": [
        "en",
        "nl",
        "fr"
      ],
      "type": "string",
      "description": "Language for names and descriptions (default en)"
    },
    "scent_id": {
      "type": "integer"
    },
    "collection_id": {
      "type": "integer"
    },
    "product_type_id": {
      "type": "integer"
    }
  }
}
    arguments 23 lines
  • get_product reads unknown 38h ago

    Full details for one product: description, price (EUR, incl. VAT), EAN, live stock, categories, page URL and all image URLs.

    mcp-tool

    {
  "type": "object",
  "required": [
    "bam_id"
  ],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "nl",
        "fr"
      ],
      "type": "string",
      "description": "Language for names and descriptions (default en)"
    },
    "bam_id": {
      "type": "integer",
      "description": "Product id from search or listing results"
    }
  }
}
    arguments 21 lines
  • search_products reads unknown 13h ago

    Fuzzy keyword search over the candle catalog. Matches product names, descriptions and EAN barcodes; multiple words must all match.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "nl",
        "fr"
      ],
      "type": "string",
      "description": "Language for names and descriptions (default en)"
    },
    "query": {
      "type": "string",
      "description": "Keywords or an EAN barcode"
    }
  }
}
    arguments 21 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 6b64191dc374f0c5.

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