Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BAM Kaarsen catalog

REMOTE · REALBAM.BE · SCANNED SEP 20

Search and browse the BAM Kaarsen candle catalog and white-label offering. Read-only, no auth.

Available components

+3 this week 75 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 302 tokens (~75/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the BAM Kaarsen catalog MCP server?

BAM Kaarsen catalog is a hosted endpoint at https://realbam.be/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · realbam.be

# add to Claude Code
claude mcp add --transport http be-realbam-catalog 'https://realbam.be/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "be-realbam-catalog": {
      "url": "https://realbam.be/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "be-realbam-catalog": {
      "type": "http",
      "url": "https://realbam.be/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.be-realbam-catalog]
url = "https://realbam.be/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "be-realbam-catalog": {
      "type": "remote",
      "url": "https://realbam.be/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add be-realbam-catalog --url 'https://realbam.be/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  be-realbam-catalog:
    url: "https://realbam.be/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "be-realbam-catalog": {
      "Transport": "http",
      "Url": "https://realbam.be/mcp"
    }
  }
}
# add to Vellum
assistant mcp add be-realbam-catalog -t streamable-http -u 'https://realbam.be/mcp'
// mcp.json
{
  "mcpServers": {
    "be-realbam-catalog": {
      "type": "http",
      "url": "https://realbam.be/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://realbam.be/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=realbam.be CN=YE1,O=Let's Encrypt,C=US 13 Aug 2026 11 Nov 2026 ECDSA 256 ECDSA-SHA384 5f0bc7ec73b34cfa2da5f462cf7efddb634
SANs: realbam.be
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of realbam.be. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
be. present 45588 13 Verified
realbam.be. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://realbam.be/mcp Verified 200
http (plaintext) http://realbam.be/mcp HTTPS enforced 308 https://realbam.be/mcp
MCP tools · 4 exposed · ~248 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
browse_catalog ~44

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

NameTypeReqDescription
langstringLanguage for names and descriptions (default en)

No output schema declared.

No examples provided.

get_product ~69

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

NameTypeReqDescription
bam_idintegeryesProduct id from search or listing results
langstringLanguage for names and descriptions (default en)

No output schema declared.

No examples provided.

list_products ~73

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

NameTypeReqDescription
collection_idinteger
langstringLanguage for names and descriptions (default en)
product_type_idinteger
scent_idinteger

No output schema declared.

No examples provided.

search_products ~62

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

NameTypeReqDescription
langstringLanguage for names and descriptions (default en)
querystringyesKeywords or an EAN barcode

No output schema declared.

No examples provided.

Common questions

What is the BAM Kaarsen catalog MCP server?

BAM Kaarsen catalog is an MCP server listed in the public MCP registry as be.realbam/catalog. Search and browse the BAM Kaarsen candle catalog and white-label offering. Read-only, no auth. This page covers its hosted endpoint (https://realbam.be/mcp).

Is the BAM Kaarsen catalog MCP server safe to use?

BAM Kaarsen catalog scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the BAM Kaarsen catalog MCP server expose?

BAM Kaarsen catalog exposes 4 tools: search_products, get_product, browse_catalog, list_products. Their descriptions and schemas cost roughly 248 tokens of context every time the server is loaded.

Does the BAM Kaarsen catalog MCP server require authentication?

No. We connected to BAM Kaarsen catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BAM Kaarsen catalog MCP server still maintained?

BAM Kaarsen catalog is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.