# CleanIngredients (remote · cleaningredients.co)

Research China-origin botanicals, supplier evidence gaps, sourcing briefs and ingredient costs.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `cleaningredients.co`: 67/100 (this document), [markdown](https://verifymcp.io/servers/burmanharry-cleaningredients/api-mcp.md), [page](https://verifymcp.io/servers/burmanharry-cleaningredients/api-mcp)

## Channel facts

- Endpoint: `https://cleaningredients.co/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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 569 tokens (~71/item across 8 items; 7 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the CleanIngredients MCP server?

CleanIngredients is a hosted endpoint at https://cleaningredients.co/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 burmanharry-cleaningredients 'https://cleaningredients.co/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "burmanharry-cleaningredients": {
      "url": "https://cleaningredients.co/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "burmanharry-cleaningredients": {
      "type": "http",
      "url": "https://cleaningredients.co/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.burmanharry-cleaningredients]
url = "https://cleaningredients.co/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "burmanharry-cleaningredients": {
      "type": "remote",
      "url": "https://cleaningredients.co/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add burmanharry-cleaningredients --url 'https://cleaningredients.co/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  burmanharry-cleaningredients:
    url: "https://cleaningredients.co/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "burmanharry-cleaningredients": {
      "Transport": "http",
      "Url": "https://cleaningredients.co/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add burmanharry-cleaningredients -t streamable-http -u 'https://cleaningredients.co/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "burmanharry-cleaningredients": {
      "type": "http",
      "url": "https://cleaningredients.co/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-11-21 (score 67, +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-11-19 (score 66, +1)

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

### 2026-11-17 (score 65, +1)

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

### 2026-11-16 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 64)

First indexed and scored.

## MCP tools (7)

### `search_ingredients` (~62 tokens)

Search botanical ingredients

Search CleanIngredients ingredient names, summaries and species notes. Includes core and later-stage research; returns status, source links and review dates. Empty query lists ingredients.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `query` (string)

### `get_ingredient` (~50 tokens)

Read ingredient evidence

Get a botanical ingredient's grades, species, buying considerations and published source reviews. Use the slug from search_ingredients. Includes actual offering counts; does not imply availability.

Input parameters:

- `slug` (string, required)

### `search_supplier_research` (~75 tokens)

Search supplier research leads

Search company-published botanical supplier research. Every result is an unconfirmed research lead with a source URL and outstanding evidence checks. No stock, price, sample or quote availability is implied.

Input parameters:

- `ingredient` (string)
- `limit` (integer)
- `offset` (integer)
- `query` (string)

### `get_evidence_coverage` (~37 tokens)

Inspect directory evidence coverage

Read current coverage counts for the core ingredients, including confirmed offerings and source reviews. These are directory counts, not market-wide statistics.

### `calculate_landed_cost` (~106 tokens)

Calculate ingredient landed cost

Estimate total and per-kg cost from buyer-provided inputs. All amounts must be in one currency. Duty is a total monetary amount, not a percentage. No live freight, duty or supplier quotes are fetched.

Input parameters:

- `currency` (string)
- `dutyAmount` (number)
- `freight` (number)
- `other` (number)
- `pricePerKg` (number, required)
- `quantityKg` (number, required)
- `testing` (number)

### `calculate_active_cost` (~83 tokens)

Calculate cost per active gram

Compare assay-based ingredient costs. Price is per kg; assay is percent (0 < assay <= 100); targetActiveMg is desired active mass per serving. This is formulation arithmetic, not dosage advice.

Input parameters:

- `assayPercent` (number, required)
- `currency` (string)
- `pricePerKg` (number, required)
- `targetActiveMg` (number, required)

### `build_sourcing_brief` (~96 tokens)

Draft a botanical sourcing brief

Generate an RFQ draft for a catalog ingredient. Returns text only: does not store personal data, submit an inquiry, contact a supplier or place an order. Review the draft before using the website inquiry form.

Input parameters:

- `application` (string)
- `destination` (string)
- `grade` (string)
- `ingredientSlug` (string, required)
- `notes` (string)
- `quantity` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 64
- 2026-11-15: 64

## Common questions

### What is the CleanIngredients MCP server?

CleanIngredients is an MCP server listed in the public MCP registry as io.github.burmanharry/cleaningredients. Research China-origin botanicals, supplier evidence gaps, sourcing briefs and ingredient costs. This page covers its hosted endpoint (https://cleaningredients.co/api/mcp).

### Is the CleanIngredients MCP server safe to use?

CleanIngredients scores 67 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 CleanIngredients MCP server expose?

CleanIngredients exposes 7 tools: search_ingredients, get_ingredient, search_supplier_research, get_evidence_coverage, calculate_landed_cost, and 2 more. Their descriptions and schemas cost roughly 509 tokens of context every time the server is loaded.

### Does the CleanIngredients MCP server require authentication?

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

### Is the CleanIngredients MCP server still maintained?

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

### What did VerifyMCP test on the CleanIngredients MCP server?

VerifyMCP ran 12 checks on CleanIngredients, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about CleanIngredients: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://cleaningredients.co/api/mcp
- Repository: https://github.com/burmanharry/cleaningredients
- Website: https://cleaningredients.co/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/burmanharry-cleaningredients/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/burmanharry-cleaningredients/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/burmanharry-cleaningredients/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/burmanharry-cleaningredients/api-mcp
