Is cbest-lighting live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is cbest-lighting free to use?

Yes — the hub reached it with no key and no payment.

What tools does cbest-lighting have?

8 tools: get_brand, classify_lighting_term, get_product, compare_brands, start_consultation, search_products, list_categories, list_brands.

Is cbest-lighting 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.

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

cbest-lighting

https://www.cbest.ir

Registry code: 91f79f9c0ac5f055

api record

Cbest Lighting is an independent advisory marketplace for lighting in Iran. This server is its supplier directory: real products, real suppliers, a Persian↔English taxonomy. It is free and needs no key.

Seven tools read: search_products, get_product, list_categories, list_brands, get_brand, compare_brands, classify_lighting_term. One acts: start_consultation.

endpoint: https://www.cbest.ir/lighting/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 cbest-lighting live?: Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is cbest-lighting free to use?: Yes — the hub reached it with no key and no payment.
What tools does cbest-lighting have?: 8 tools: get_brand, classify_lighting_term, get_product, compare_brands, start_consultation, search_products, list_categories, list_brands.
Is cbest-lighting 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

99.6%

90 days 99.1%· all time 99.1%

latency

675ms

last good check

priced tools

of 8 tools

_ answered our checks, 90 days 439 checks · signed record

2026-10-20 23:12 degraded → live
2026-10-20 21:55 live → degraded· timeout after 20000ms
2026-10-12 10:24 degraded → live
2026-09-27 16:20 degraded → live
2026-09-27 15:17 live → degraded· timeout after 20000ms

_ what it is for

topic: productivity & business procurement & sourcing
used for: search lighting products from iranian suppliers
compare lighting brands by category
classify a lighting term
start a lighting consultation
takes → gives: text → data
tools: 7 reads1 changes data

_ 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

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 8 tools

3 open 5 never probed 3 of 8 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.

search_products reads open 17h ago

Search the catalog of real products stocked by the suppliers on file. Accepts Persian or English. Returns normalized facets (mounting, indoor/outdoor, IP, colour temperature, and wattage/lumen where stated) plus what the query matched on. Colour temperature is returned but is NOT filterable: a fixture is usually sold in several, and the row carries the one its source printed. The response always reports what the filters excluded and why, split into 'not stated in our data' and 'did not match' — a product missing from a result is NEVER evidence that a supplier does not make it; use get_brand's doesNotDo for that.

mcp-tool

{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "Free text in Persian or English, e.g. «چراغ خطی توکار» or 'recessed linear profile'."
    },
    "brand": {
      "enum": [
        "spl",
        "mazinoor",
        "nooran",
        "shoa",
        "candle",
        "setareh-shomal",
        "eslight",
        "beco"
      ],
      "type": "string",
      "description": "Restrict to one supplier."
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Results per page (default 20, max 50)."
    },
    "ip_min": {
      "type": "integer",
      "maximum": 69,
      "minimum": 20,
      "description": "Minimum IP rating, e.g. 65 for a wet location."
    },
    "offset": {
      "type": "integer",
      "maximum": 5000,
      "minimum": 0,
      "description": "Pagination offset; use nextOffset from the previous call."
    },
    "category": {
      "enum": [
        "downlight",
        "wall",
        "magnetic",
        "linear",
        "pendant",
        "bollard",
        "ceiling-surface",
        "plaster-frame",
        "inground",
        "accessory",
        "track",
        "portable",
        "lamp",
        "street",
        "strip-profile",
        "industrial",
        "stair",
        "floodlight",
        "facade",
        "panel"
      ],
      "type": "string",
      "description": "One of the 20 canonical categories — see list_categories."
    },
    "mounting": {
      "enum": [
        "inground",
        "magnetic",
        "track",
        "pendant",
        "semi-recessed",
        "recessed",
        "surface",
        "wall",
        "pole",
        "spike",
        "portable"
      ],
      "type": "string",
      "description": "How it mounts."
    },
    "has_image": {
      "type": "boolean",
      "description": "Only products with an image on file."
    },
    "price_tier": {
      "enum": [
        "budget",
        "mid",
        "premium"
      ],
      "type": "string",
      "description": "The price band the SUPPLIER declared for its whole range. Self-declared and per brand, not per product, and not a quoted price — no supplier on file publishes prices."
    },
    "environment": {
      "enum": [
        "indoor",
        "outdoor",
        "both"
      ],
      "type": "string",
      "description": "indoor, outdoor, or both. 'indoor' also returns fixtures rated for both."
    }
  },
  "additionalProperties": false
}

arguments 107 lines

list_categories reads open 17h ago
The 20 canonical categories with Persian and English names, product counts, and which suppliers are in each. Small enough to fetch once and reason over the whole market; flags categories that only one supplier covers.

mcp-tool
{ "type": "object", "properties": {}, "additionalProperties": false }
arguments 5 lines
list_brands reads open 17h ago
Every supplier on file with what they cover, how complete their data is, and when it was last read. No contact details — see the server instructions.

mcp-tool
{ "type": "object", "properties": {}, "additionalProperties": false }
arguments 5 lines
get_brand reads unknown 15h ago
One supplier in full: what they make, the product families they run, and — the field worth the call — doesNotDo, a statement of what they genuinely do NOT make, computed from absence in their product list rather than inferred from their marketing.

mcp-tool
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Supplier slug from list_brands." } }, "additionalProperties": false }
arguments 13 lines
classify_lighting_term reads unknown never probed
Map any Persian or English lighting phrase onto the canonical taxonomy — «داون‌لایت توکار», 'trimless plaster frame', 'high bay'. Backed by 522 learned type→category pairs plus rules measured at 95% agreement. Returns null for a phrase that names no category rather than guessing.

mcp-tool
{ "type": "object", "required": [ "term" ], "properties": { "term": { "type": "string", "description": "A product type, in Persian or English." } }, "additionalProperties": false }
arguments 13 lines
get_product reads unknown 15h ago
Every field on file for one product, by the id search_products returns ('brand/product-slug'), including provenance: whether the fact came from the supplier's own website or from a page of their PDF catalog, and when it was read.

mcp-tool
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Product id, e.g. 'spl/hangwire-puzzle-hangwire'." } }, "additionalProperties": false }
arguments 13 lines

compare_brands reads unknown never probed

Which suppliers cover a category, with counts, share, and per-facet data coverage. Coverage describes what each supplier's SOURCE stated, never product quality, and a one-supplier category says so rather than pretending to be a comparison.

mcp-tool

{
  "type": "object",
  "required": [
    "category"
  ],
  "properties": {
    "category": {
      "enum": [
        "downlight",
        "wall",
        "magnetic",
        "linear",
        "pendant",
        "bollard",
        "ceiling-surface",
        "plaster-frame",
        "inground",
        "accessory",
        "track",
        "portable",
        "lamp",
        "street",
        "strip-profile",
        "industrial",
        "stair",
        "floodlight",
        "facade",
        "panel"
      ],
      "type": "string",
      "description": "Category slug from list_categories."
    }
  },
  "additionalProperties": false
}

arguments 35 lines

start_consultation changes data unknown never probed

Turn a described need into a link the person opens themselves, where an adviser builds a brief and matches it against suppliers' real stock. This is how someone actually reaches a supplier: there are no contact details in this server, and this call does not contact anyone. It stores nothing and it REFUSES any personal data — no name, no number, no email. Describe the project, not the person.

mcp-tool

{
  "type": "object",
  "required": [
    "need"
  ],
  "properties": {
    "need": {
      "type": "string",
      "description": "The project in the person's own terms, in Persian or English — space, use, style, constraints. No personal details: the call is refused if it contains a phone number, an email or a handle."
    },
    "client": {
      "type": "string",
      "description": "Optional: a short name for your app, so we can tell which assistants send people here. Self-reported, lowercase slug."
    }
  },
  "additionalProperties": false
}

arguments 17 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.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
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.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 91f79f9c0ac5f055.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/91f79f9c0ac5f055/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/91f79f9c0ac5f055/badge.svg)](https://brick.blue/agent/91f79f9c0ac5f055?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

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.