# ir.cbest/lighting (remote · www.cbest.ir)

Iranian lighting supplier directory: products, brands, and a bilingual Persian/English taxonomy.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `www.cbest.ir`: 70/100 (this document), [markdown](https://verifymcp.io/servers/ir-cbest-lighting/lighting-api-mcp.md), [page](https://verifymcp.io/servers/ir-cbest-lighting/lighting-api-mcp)

## Channel facts

- Endpoint: `https://www.cbest.ir/lighting/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1346 tokens (~134/item across 10 items; 8 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the ir.cbest/lighting MCP server?

ir.cbest/lighting is a hosted endpoint at https://www.cbest.ir/lighting/api/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.

### Claude

```bash
claude mcp add --transport http ir-cbest-lighting 'https://www.cbest.ir/lighting/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ir-cbest-lighting": {
      "url": "https://www.cbest.ir/lighting/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ir-cbest-lighting": {
      "type": "http",
      "url": "https://www.cbest.ir/lighting/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ir-cbest-lighting]
url = "https://www.cbest.ir/lighting/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ir-cbest-lighting": {
      "type": "remote",
      "url": "https://www.cbest.ir/lighting/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ir-cbest-lighting --url 'https://www.cbest.ir/lighting/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ir-cbest-lighting:
    url: "https://www.cbest.ir/lighting/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ir-cbest-lighting": {
      "Transport": "http",
      "Url": "https://www.cbest.ir/lighting/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ir-cbest-lighting -t streamable-http -u 'https://www.cbest.ir/lighting/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ir-cbest-lighting": {
      "type": "http",
      "url": "https://www.cbest.ir/lighting/api/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 70, +1)

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

### 2026-09-25 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 69, +1)

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

### 2026-09-22 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-21 (score 67)

First indexed and scored.

## MCP tools (8)

### `search_products` (~344 tokens)

Search lighting products

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) 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.

Input parameters:

- `brand` (string): Restrict to one supplier.
- `category` (string): One of the 20 canonical categories — see list_categories.
- `environment` (string): indoor, outdoor, or both. 'indoor' also returns fixtures rated for both.
- `has_image` (boolean): Only products with an image on file.
- `ip_min` (integer): Minimum IP rating, e.g. 65 for a wet location.
- `limit` (integer): Results per page (default 20, max 50).
- `mounting` (string): How it mounts.
- `offset` (integer): Pagination offset; use nextOffset from the previous call.
- `price_tier` (string): 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.
- `q` (string): Free text in Persian or English, e.g. «چراغ خطی توکار» or 'recessed linear profile'.

### `get_product` (~79 tokens)

Get one product

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.

Input parameters:

- `id` (string, required): Product id, e.g. 'spl/hangwire-puzzle-hangwire'.

### `list_categories` (~49 tokens)

List the lighting categories

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.

### `list_brands` (~40 tokens)

List the suppliers

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.

### `get_brand` (~72 tokens)

Get a supplier profile

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.

Input parameters:

- `slug` (string, required): Supplier slug from list_brands.

### `compare_brands` (~68 tokens)

Compare suppliers in a category

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.

Input parameters:

- `category` (string, required): Category slug from list_categories.

### `classify_lighting_term` (~88 tokens)

Classify a lighting term

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.

Input parameters:

- `term` (string, required): A product type, in Persian or English.

### `start_consultation` (~171 tokens)

Get the person a link to real advice

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.

Input parameters:

- `client` (string): Optional: a short name for your app, so we can tell which assistants send people here. Self-reported, lowercase slug.
- `need` (string, required): 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ir-cbest-lighting/lighting-api-mcp#diagnostics

## Score history

- 2026-09-28: 70
- 2026-09-27: 70
- 2026-09-26: 69
- 2026-09-25: 69
- 2026-09-24: 69
- 2026-09-23: 68
- 2026-09-22: 68
- 2026-09-21: 67

## Common questions

### What is the ir.cbest/lighting MCP server?

ir.cbest/lighting is an MCP server listed in the public MCP registry as ir.cbest/lighting. Iranian lighting supplier directory: products, brands, and a bilingual Persian/English taxonomy. This page covers its hosted endpoint (https://www.cbest.ir/lighting/api/mcp).

### Is the ir.cbest/lighting MCP server safe to use?

ir.cbest/lighting scores 70 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 ir.cbest/lighting MCP server expose?

ir.cbest/lighting exposes 8 tools: search_products, get_product, list_categories, list_brands, get_brand, and 3 more. Their descriptions and schemas cost roughly 911 tokens of context every time the server is loaded.

### Does the ir.cbest/lighting MCP server require authentication?

No. We connected to ir.cbest/lighting without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ir.cbest/lighting MCP server still maintained?

ir.cbest/lighting is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.cbest.ir/lighting/api/mcp
- Website: https://www.cbest.ir/lighting/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ir-cbest-lighting/lighting-api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ir-cbest-lighting/lighting-api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ir-cbest-lighting/lighting-api-mcp