Verdict
REMOTE · VERDICT.ALLTHEPOSSIBLES.COM
Design review as MCP tools: critique, states, journeys, UI copy, PRD assumptions. BYOK or hosted.
Available components
Last scanned (12 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Design and Media
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 513 tokens (~85/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +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.
- 21 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 +40
- Authorization: unverified → partial ▲ security
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 19 Oct 26 28
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://verdict.allthepossibles.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=allthepossibles.com | CN=WE1,O=Google Trust Services,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6298e41f8e68f5750e80f250c4c4397a |
| SANs: allthepossibles.com, verdict.allthepossibles.com, *.verdict.allthepossibles.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of verdict.allthepossibles.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| allthepossibles.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://verdict.allthepossibles.com/mcp | Verified | 200 | |
| http (plaintext) | http://verdict.allthepossibles.com/mcp | HTTPS enforced | 301 | https://verdict.allthepossibles.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_copy Audit copy ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| strings | array | yes | – |
No output schema declared.
No examples provided.
check_terminology Check terminology ~52
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sources | array | yes | – |
No output schema declared.
No examples provided.
critique_experience Critique experience ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact | object | yes | 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. |
No output schema declared.
No examples provided.
find_assumptions Find assumptions ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| prd_text | string | yes | The PRD, brief or proposal. |
No output schema declared.
No examples provided.
generate_state_matrix Generate state matrix ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| feature_description | string | yes | The feature, form or screen, in prose or as a spec. |
| known_dimensions | array | – | Optional: dimensions you already cover, so they are skipped. |
No output schema declared.
No examples provided.
map_journey Map journey ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| objective | string | yes | What the person is trying to accomplish, in their words. |
| user_maturity | string | – | – |
No output schema declared.
No examples provided.
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.
remote · verdict.allthepossibles.com
claude mcp add --transport http com-allthepossibles-verdict 'https://verdict.allthepossibles.com/mcp'
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.