# io.github.liquidgrails/lqd-verdict (remote · lqd-verdict.onrender.com)

An independent yes-or-no style verdict, with a short reason, on a men's clothing item or outfit.

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

## Components

- remote · `lqd-verdict.onrender.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/liquidgrails-lqd-verdict/lqd-verdict.md), [page](https://verifymcp.io/servers/liquidgrails-lqd-verdict/lqd-verdict)

## Channel facts

- Endpoint: `https://lqd-verdict.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-05.

- **Endpoint Security**: 57/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 1 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.
  - 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**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 199 tokens (~199/item across 1 items; 1 tools + 0 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**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 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 io.github.liquidgrails/lqd-verdict MCP server?

io.github.liquidgrails/lqd-verdict is a hosted endpoint at https://lqd-verdict.onrender.com/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 liquidgrails-lqd-verdict 'https://lqd-verdict.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "liquidgrails-lqd-verdict": {
      "url": "https://lqd-verdict.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "liquidgrails-lqd-verdict": {
      "type": "http",
      "url": "https://lqd-verdict.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.liquidgrails-lqd-verdict]
url = "https://lqd-verdict.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "liquidgrails-lqd-verdict": {
      "type": "remote",
      "url": "https://lqd-verdict.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add liquidgrails-lqd-verdict --url 'https://lqd-verdict.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  liquidgrails-lqd-verdict:
    url: "https://lqd-verdict.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "liquidgrails-lqd-verdict": {
      "Transport": "http",
      "Url": "https://lqd-verdict.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add liquidgrails-lqd-verdict -t streamable-http -u 'https://lqd-verdict.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "liquidgrails-lqd-verdict": {
      "type": "http",
      "url": "https://lqd-verdict.onrender.com/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-05 (score 65, +2)

- [functional regression] Schema quality: 151 → 199
- [functional improvement] Tool coverage: 57% → 63%
- [cosmetic] “lqd_verdict” added an optional parameter “recipient”
- [cosmetic] “lqd_verdict” reworded the description of “description”

### 2026-11-03 (score 63, +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-01 (score 62, 0)

- [functional regression] Schema quality: 107 → 151
- [functional improvement] Tool coverage: 40% → 57%
- [cosmetic] “lqd_verdict” added an optional parameter “example_id”
- [cosmetic] “lqd_verdict” added an optional parameter “previous_verdict_id”

### 2026-10-31 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 61)

First indexed and scored.

## MCP tools (1)

### `lqd_verdict` (~199 tokens)

An independent yes-or-no style verdict, with a short reason, on a men's clothing item or outfit. Called by an agent before purchase. No affiliate cut, no placement fees.

Input parameters:

- `context` (object)
- `description` (string, required): Piece or look, comma-separated pieces work best (color, fabric, shoe). For a gift check, this is the gift.
- `example_id` (string): Optional caller id for this example. Echoed back. Not required.
- `image_path` (string)
- `options` (array): If set, LQD picks one (OPTIONS).
- `previous_verdict_id` (string): Optional id of an earlier verdict. Echoed back. Not required.
- `product_url` (string)
- `recipient` (string): Optional one-line style note for a gift check, such as classic daytime clothes and loafers. Same price. LQD does not treat this as a wardrobe.

## Diagnostics

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

## Score history

- 2026-11-05: 65
- 2026-11-04: 63
- 2026-11-03: 63
- 2026-11-02: 62
- 2026-11-01: 62
- 2026-10-31: 62
- 2026-10-30: 61

## Common questions

### What is the io.github.liquidgrails/lqd-verdict MCP server?

io.github.liquidgrails/lqd-verdict is an MCP server listed in the public MCP registry as io.github.liquidgrails/lqd-verdict. An independent yes-or-no style verdict, with a short reason, on a men's clothing item or outfit. This page covers its hosted endpoint (https://lqd-verdict.onrender.com/mcp).

### Is the io.github.liquidgrails/lqd-verdict MCP server safe to use?

io.github.liquidgrails/lqd-verdict scores 65 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 io.github.liquidgrails/lqd-verdict MCP server expose?

io.github.liquidgrails/lqd-verdict exposes 1 tool: lqd_verdict. Their descriptions and schemas cost roughly 199 tokens of context every time the server is loaded.

### Does the io.github.liquidgrails/lqd-verdict MCP server require authentication?

No. We connected to io.github.liquidgrails/lqd-verdict without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.liquidgrails/lqd-verdict MCP server still maintained?

io.github.liquidgrails/lqd-verdict 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.

### What did VerifyMCP test on the io.github.liquidgrails/lqd-verdict MCP server?

VerifyMCP ran 12 checks on io.github.liquidgrails/lqd-verdict, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.liquidgrails/lqd-verdict: Authorization. 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://lqd-verdict.onrender.com/mcp
- Repository: https://github.com/liquidgrails/lqd-verdict-tool
- Changelog RSS feed: https://verifymcp.io/servers/liquidgrails-lqd-verdict/lqd-verdict.xml
- Changelog JSON feed: https://verifymcp.io/servers/liquidgrails-lqd-verdict/lqd-verdict/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/liquidgrails-lqd-verdict/lqd-verdict.json
- HTML version of this page: https://verifymcp.io/servers/liquidgrails-lqd-verdict/lqd-verdict