Blender integration through the Model Context Protocol
Nothing to run from here
Verdict is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
6
tools declared
remote
at its publisher
—
calls last 7d
What it does
Design review as MCP tools: critique, states, journeys, UI copy, PRD assumptions. BYOK or hosted.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http allthepossibles-verdict-mcp https://verdict.allthepossibles.com/mcp
# 2 — ask your agent for something these tools do
# critique_experience, generate_state_matrix, map_journey and 3 more
Verdict costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ALAll 6 servers
allthepossibles6 servers
4 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http allthepossibles-verdict-mcp https://verdict.allthepossibles.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take Authorization header (Optional. Bearer vd_... for Basic or Pro; two free reviews a day with no key. Install steps per client: https://verdict.allthepossibles.com/docs#install) if you want to set it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| artifact | object | yes | The design under review. |
| prd | string | no | Optional brief or PRD. Without one, the review judges against general principles. |
| context | string | no | Optional: audience, the single most important action, viewport. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feature_description | string | yes | The feature, form or screen, in prose or as a spec. |
| known_dimensions | array | no | Optional: dimensions you already cover, so they are skipped. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| objective | string | yes | What the person is trying to accomplish, in their words. |
| user_maturity | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| strings | array | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prd_text | string | yes | The PRD, brief or proposal. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sources | array | yes | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Verdict or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.1.0 · scanned 30 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestb6cec3eaac982d4b4a8fb36b982596749df9d86ddb94225bc325fd5fbf23d477
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| critique_experience | no tags | |
| generate_state_matrix | no tags | |
| map_journey | no tags | |
| audit_copy | no tags | |
| find_assumptions | no tags | |
| check_terminology | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestb6cec3eaac982d4b
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Verdict can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.