Lavenders MCP

A read-only MCP server providing access to Lavenders (LAVNDR120) digital market data. It allows agents to retrieve brand overviews, list and view packages, access FAQs, and fetch the live consumer index card without requiring authentication.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Community listingStreamable HTTPNo sign-inEndpoint checked 2026-11-02Published by Lavenders

MCP endpoint (Streamable HTTP)

https://lavndr.omssolutionorders.workers.dev/mcp

Vendor documentation

What its tools do

5 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (5)

get_brand_overview
list_packages
get_package
get_faq
get_live_index

5 of 5 have a description · 0 of 5 declare behavior hints · 0 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 2, 2026, 4:31 AM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Retrieve brand overview information
List available market packages
Get details for a specific package
Fetch the live consumer index data

Source and maintenance

Community listingRegistry 1.0.0

mcp-registry: io.github.lavndrs120/lavenders@1.0.0 Source repository Project website

Last repository push: Nov 2, 2026, 1:26 PM UTC
Maintenance checked: Nov 2, 2026, 5:01 PM UTC

Protocol and capabilities

Server: lavenders 1.0.0
MCP protocol negotiated in check: 2025-06-18
Tools: 5 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Lavenders is a digital market system that brings together 120 businesses and brands in one market. Each business runs its own order-management app (OMS); their real orders feed one live consumer index called LAVNDR120. Lavenders is the brand; LAVNDR120 is the index. Unrelated to lavender plants or oil. No buying, selling or trading of shares on the platform. Informational only: not investment advice and no promise of profit or returns. Terms and agreements are drafts pending legal review. Prices are as of 1 November 2026; the home page is the source of truth.

Tools

5 advertised

get_brand_overview

Advertised by the server during the last successful anonymous check.

What Lavenders (LAVNDR120) is, plus the rules any answer must respect.

get_brand_overview input schema

{
  "type": "object",
  "properties": {}
}

list_packages

Advertised by the server during the last successful anonymous check.

The seven packages (Lava, Vindex, Magma, OMS, Reseller, Franchise, Tycoon) with prices and seats.

list_packages input schema

{
  "type": "object",
  "properties": {}
}

get_package

Advertised by the server during the last successful anonymous check.

One package by id: lava, vindex, magma, oms, reseller, franchise or tycoon.

get_package input schema

{
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "enum": [
        "lava",
        "vindex",
        "magma",
        "oms",
        "reseller",
        "franchise",
        "tycoon"
      ],
      "type": "string"
    }
  }
}

get_faq

Advertised by the server during the last successful anonymous check.

Frequently asked questions, including what the platform does not offer.

get_faq input schema

{
  "type": "object",
  "properties": {}
}

get_live_index

Advertised by the server during the last successful anonymous check.

Current LAVNDR120 index card (net asset value and day change). Informational only.

get_live_index input schema

{
  "type": "object",
  "properties": {}
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (5 of 5 answered).

2026-11-02: 3 of 3 checks answered
2026-11-03: 2 of 2 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 293 ms
95th percentile latency: 293 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 2, 2026, 5:01 PM UTC · repository · passed · metadata changed · updated
Nov 2, 2026, 5:01 PM UTC · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown
Nov 2, 2026, 4:31 AM UTC · probe · passed · 293 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http lavenders-mcp https://lavndr.omssolutionorders.workers.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add lavenders-mcp --url https://lavndr.omssolutionorders.workers.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable lavenders-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "lavenders-mcp": {
      "type": "streamableHttp",
      "url": "https://lavndr.omssolutionorders.workers.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start lavenders-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http lavenders-mcp https://lavndr.omssolutionorders.workers.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "lavenders-mcp": {
      "serverUrl": "https://lavndr.omssolutionorders.workers.dev/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Lavenders MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows