# Verdict (remote · verdict.allthepossibles.com)

Design review as MCP tools: critique, states, journeys, UI copy, PRD assumptions. BYOK or hosted.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

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

## Channel facts

- Endpoint: `https://verdict.allthepossibles.com/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-10-23.

- **Endpoint Security**: 74/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 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**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 513 tokens (~85/item across 6 items; 6 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**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 70% 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 6 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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

Verdict is a hosted endpoint at https://verdict.allthepossibles.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 com-allthepossibles-verdict 'https://verdict.allthepossibles.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-allthepossibles-verdict": {
      "url": "https://verdict.allthepossibles.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-allthepossibles-verdict:
    url: "https://verdict.allthepossibles.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-allthepossibles-verdict": {
      "type": "http",
      "url": "https://verdict.allthepossibles.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-10-22 (score 69, +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-10-21 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-20 (score 68, +40)

- [security improvement] Authorization: unverified → partial
- [security improvement] HTTPS: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 70
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good

### 2026-10-19 (score 28)

First indexed and scored.

## MCP tools (6)

### `critique_experience` (~139 tokens)

Critique experience

Adversarial critique of a design, given as a description or a screenshot URL, with an optional PRD. Returns findings ranked by severity covering hierarchy, density, affordance, composition, copy, and the first-use / 500th-use / zero-data / huge-data / no-permission / irreversible questions. Call it before presenting a design to a human or handing it to engineering.

Input parameters:

- `artifact` (object, required): The design under review.
- `context` (string): Optional: audience, the single most important action, viewport.
- `prd` (string): Optional brief or PRD. Without one, the review judges against general principles.

### `generate_state_matrix` (~113 tokens)

Generate state matrix

Generates the state space for a feature, form or screen across data, loading, permission, network, account, content, time, concurrency, outside dependencies, money, consistency and people, and lists the gaps most likely to cause real harm. Call it when a feature is described and you want to know what nobody drew.

Input parameters:

- `feature_description` (string, required): The feature, form or screen, in prose or as a spec.
- `known_dimensions` (array): Optional: dimensions you already cover, so they are skipped.

### `map_journey` (~87 tokens)

Map journey

Breaks a user objective into the stages of a real journey and flags entry points and exit paths that have no designed arrival or recovery. Optionally focuses on one user maturity (first use, occasional, habitual, expert). Describes behavior, not screens.

Input parameters:

- `objective` (string, required): What the person is trying to accomplish, in their words.
- `user_maturity` (string)

### `audit_copy` (~58 tokens)

Audit copy

Per-string critique of interface copy: buttons, errors, empty states, confirmations, notifications. Each string comes back with the problem and a fix, or nothing if it already works. Call it before shipping UI strings.

Input parameters:

- `strings` (array, required)

### `find_assumptions` (~64 tokens)

Find assumptions

Reads a PRD or design brief and extracts the unverified assumptions inside it, ranked by risk, each turned into a research question that could change a decision. Never simulates user answers.

Input parameters:

- `prd_text` (string, required): The PRD, brief or proposal.

### `check_terminology` (~52 tokens)

Check terminology

Finds concepts that carry different names across surfaces (UI strings, docs, API reference, support macros) and flags drift. Pass the text from each surface; nothing needs connecting.

Input parameters:

- `sources` (array, required)

## Diagnostics

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

## Score history

- 2026-10-23: 69
- 2026-10-22: 69
- 2026-10-21: 68
- 2026-10-20: 68
- 2026-10-19: 28

## Common questions

### What is the Verdict MCP server?

Verdict is an MCP server listed in the public MCP registry as com.allthepossibles/verdict. Design review as MCP tools: critique, states, journeys, UI copy, PRD assumptions. BYOK or hosted. This page covers its hosted endpoint (https://verdict.allthepossibles.com/mcp).

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

Verdict scores 69 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 Verdict MCP server expose?

Verdict exposes 6 tools: critique_experience, generate_state_matrix, map_journey, audit_copy, find_assumptions, check_terminology. Their descriptions and schemas cost roughly 513 tokens of context every time the server is loaded.

### Does the Verdict MCP server require authentication?

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

### Is the Verdict MCP server still maintained?

Verdict is still listed as active in the MCP registry. We last reached this channel on 23 October 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://verdict.allthepossibles.com/mcp
- Website: https://verdict.allthepossibles.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-allthepossibles-verdict/verdict.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-allthepossibles-verdict/verdict.json
- HTML version of this page: https://verifymcp.io/servers/com-allthepossibles-verdict/verdict