# Lavenders (LAVNDR120) (remote · lavndr.omssolutionorders.workers.dev)

Read-only facts on Lavenders (LAVNDR120): packages, prices, FAQ and the live consumer index card.

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

## Components

- remote · `lavndr.omssolutionorders.workers.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/lavndrs120-lavenders/lavndr.md), [page](https://verifymcp.io/servers/lavndrs120-lavenders/lavndr)

## Channel facts

- Endpoint: `https://lavndr.omssolutionorders.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-05.

- **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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 545 tokens (~109/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 Lavenders (LAVNDR120) MCP server?

Lavenders (LAVNDR120) is a hosted endpoint at https://lavndr.omssolutionorders.workers.dev/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 lavndrs120-lavenders 'https://lavndr.omssolutionorders.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "lavndrs120-lavenders": {
      "url": "https://lavndr.omssolutionorders.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lavndrs120-lavenders": {
      "type": "http",
      "url": "https://lavndr.omssolutionorders.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.lavndrs120-lavenders]
url = "https://lavndr.omssolutionorders.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lavndrs120-lavenders": {
      "type": "remote",
      "url": "https://lavndr.omssolutionorders.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lavndrs120-lavenders --url 'https://lavndr.omssolutionorders.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lavndrs120-lavenders:
    url: "https://lavndr.omssolutionorders.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "lavndrs120-lavenders": {
      "Transport": "http",
      "Url": "https://lavndr.omssolutionorders.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lavndrs120-lavenders -t streamable-http -u 'https://lavndr.omssolutionorders.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "lavndrs120-lavenders": {
      "type": "http",
      "url": "https://lavndr.omssolutionorders.workers.dev/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-04 (score 68, +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-03 (score 67, +13)

- [security improvement] Authorization: unverified → partial
- [security] Tool “get_brand_overview” rewrote its description, which is the text the model reads
- [security] Tool “get_faq” rewrote its description, which is the text the model reads
- [security] Tool “get_live_index” rewrote its description, which is the text the model reads
- [security] Tool “get_package” rewrote its description, which is the text the model reads
- [security] Tool “list_packages” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 55 → 109
- [functional improvement] Tool coverage: 0% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: fair → good
- [cosmetic] “get_package” reworded the description of “id”

### 2026-11-02 (score 54)

First indexed and scored.

## MCP tools (5)

### `get_brand_overview` (~84 tokens)

Returns a short description of what Lavenders (LAVNDR120) is, the difference between the brand and the index, and the rules any answer about it must respect (no buying, selling or trading of shares; no promise of profit or return). Call this first when the user asks what Lavenders or LAVNDR120 is. Takes no arguments.

### `list_packages` (~90 tokens)

Lists all seven packages (Lava, Vindex, Magma, OMS, Reseller, Franchise, Tycoon) in one response, each with its id, name, one-line summary, price, number of seats where limited, and page URL, plus the disclaimers. Use it to compare packages or to find a package id; use get_package when only one package is needed. Takes no arguments.

### `get_package` (~105 tokens)

Returns one package by its id: name, one-line summary, price, number of seats where limited, and page URL, plus the disclaimers. Use list_packages first if the id is unknown. Returns an error for an id that is not one of the seven.

Input parameters:

- `id` (string, required): Package id, lowercase. One of: lava (daily access), vindex (Oracle reports), magma (activity directory), oms (business order management), reseller, franchise, tycoon.

### `get_faq` (~63 tokens)

Returns the frequently asked questions and short answers about Lavenders, LAVNDR120, OMS and the app, including what the platform does not offer. Use it for general or policy-style questions; use get_package for pricing of a specific package. Takes no arguments.

### `get_live_index` (~76 tokens)

Returns the current LAVNDR120 index card (net asset value in USD, change, percent change, day high and low) as published on the live site, with its as-of timestamp, or available:false if unavailable. Informational only, not investment advice, and not an offer to buy or sell. Takes no arguments.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lavndrs120-lavenders/lavndr#diagnostics

## Score history

- 2026-11-05: 68
- 2026-11-04: 68
- 2026-11-03: 67
- 2026-11-02: 54

## Common questions

### What is the Lavenders (LAVNDR120) MCP server?

Lavenders (LAVNDR120) is an MCP server listed in the public MCP registry as io.github.lavndrs120/lavenders. Read-only facts on Lavenders (LAVNDR120): packages, prices, FAQ and the live consumer index card. This page covers its hosted endpoint (https://lavndr.omssolutionorders.workers.dev/mcp).

### Is the Lavenders (LAVNDR120) MCP server safe to use?

Lavenders (LAVNDR120) scores 68 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 Lavenders (LAVNDR120) MCP server expose?

Lavenders (LAVNDR120) exposes 5 tools: get_brand_overview, list_packages, get_package, get_faq, get_live_index. Their descriptions and schemas cost roughly 418 tokens of context every time the server is loaded.

### Does the Lavenders (LAVNDR120) MCP server require authentication?

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

### Is the Lavenders (LAVNDR120) MCP server still maintained?

Lavenders (LAVNDR120) is still listed as active in the MCP registry. We last reached this channel on 5 November 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://lavndr.omssolutionorders.workers.dev/mcp
- Repository: https://github.com/lavndrs120/lavndrs120.github.io
- Website: https://lavndrs120.github.io/
- Changelog RSS feed: https://verifymcp.io/servers/lavndrs120-lavenders/lavndr.xml
- Changelog JSON feed: https://verifymcp.io/servers/lavndrs120-lavenders/lavndr.json
- HTML version of this page: https://verifymcp.io/servers/lavndrs120-lavenders/lavndr