# io.github.lazymac2x/llm-output-quality-monitor (remote · api.lazy-mac.com)

Cloudflare Workers MCP server: llm-output-quality-monitor

- Trust score: 55/100 (low)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.lazy-mac.com`: 55/100 (this document), [markdown](https://verifymcp.io/servers/lazymac2x-llm-output-quality-monitor/llm-output-quality-monitor-mcp.md), [page](https://verifymcp.io/servers/lazymac2x-llm-output-quality-monitor/llm-output-quality-monitor-mcp)

## Channel facts

- Endpoint: `https://api.lazy-mac.com/llm-output-quality-monitor/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-08-03.

- **Endpoint Security**: 46/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 5 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 check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 279 tokens (~55/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http lazymac2x-llm-output-quality-monitor https://api.lazy-mac.com/llm-output-quality-monitor/mcp
```

### Codex

```toml
[mcp_servers.lazymac2x-llm-output-quality-monitor]
url = "https://api.lazy-mac.com/llm-output-quality-monitor/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lazymac2x-llm-output-quality-monitor": {
      "type": "remote",
      "url": "https://api.lazy-mac.com/llm-output-quality-monitor/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lazymac2x-llm-output-quality-monitor --url https://api.lazy-mac.com/llm-output-quality-monitor/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lazymac2x-llm-output-quality-monitor:
    url: "https://api.lazy-mac.com/llm-output-quality-monitor/mcp"
```

### Other

```json
{
  "mcpServers": {
    "lazymac2x-llm-output-quality-monitor": {
      "type": "http",
      "url": "https://api.lazy-mac.com/llm-output-quality-monitor/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-08-02 (score 55, +1)

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

### 2026-07-31 (score 54, −1)

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

### 2026-07-30 (score 55, 0)

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

### 2026-07-29 (score 55, +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-07-28 (score 54, +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-07-27 (score 53, 0)

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

### 2026-07-26 (score 53)

First indexed and scored.

## MCP tools (5)

### `quality_validator` (~80 tokens)

Validate LLM response quality based on length, format, and structure

Input parameters:

- `maxLength` (number): Maximum response length (default: 10000)
- `minLength` (number): Minimum response length (default: 10)
- `response` (string, required): LLM response to validate
- `strictFormat` (boolean): Enforce punctuation and capitalization

### `drift_detector` (~63 tokens)

Detect quality drift between current and previous LLM responses

Input parameters:

- `currentResponse` (string, required): Current LLM response
- `previousResponse` (string, required): Previous LLM response
- `threshold` (number): Drift threshold (0-1, default: 0.15)

### `hallucination_scorer` (~72 tokens)

Pattern-based heuristic risk scoring for LLM responses (0-100). Detects linguistic signals such as contradictory assertions, unsourced claims, and uncertainty markers. Not a semantic hallucination detector.

Input parameters:

- `context` (string): Reference context for grounding
- `response` (string, required): LLM response to analyze

### `schema_enforcer` (~36 tokens)

Validate JSON response against schema

Input parameters:

- `response` (string, required): JSON response to validate
- `schema` (object, required): JSON schema definition

### `consistency_check` (~28 tokens)

Check consistency across multiple LLM responses

Input parameters:

- `responses` (array, required): Array of responses to compare

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lazymac2x-llm-output-quality-monitor/llm-output-quality-monitor-mcp#diagnostics

## Score history

- 2026-08-03: 55
- 2026-08-02: 55
- 2026-08-01: 54
- 2026-07-31: 54
- 2026-07-30: 55
- 2026-07-29: 55
- 2026-07-28: 54
- 2026-07-27: 53
- 2026-07-26: 53

## Links

- Remote endpoint: https://api.lazy-mac.com/llm-output-quality-monitor/mcp
- Repository: https://github.com/lazymac2x/llm-output-quality-monitor-api
- Changelog RSS feed: https://verifymcp.io/servers/lazymac2x-llm-output-quality-monitor/llm-output-quality-monitor-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/lazymac2x-llm-output-quality-monitor/llm-output-quality-monitor-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/lazymac2x-llm-output-quality-monitor/llm-output-quality-monitor-mcp