# brief bar_ (remote · briefs.welance.com)

Free bar for digital product briefs: your model judges, open rules and code score it.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `briefs.welance.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-welance-perfect-brief/briefs.md), [page](https://verifymcp.io/servers/com-welance-perfect-brief/briefs)

## Channel facts

- Endpoint: `https://briefs.welance.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.14.1`

## 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**: 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**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1045 tokens (~95/item across 11 items; 7 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the brief bar_ MCP server?

brief bar_ is a hosted endpoint at https://briefs.welance.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-welance-perfect-brief 'https://briefs.welance.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-welance-perfect-brief": {
      "url": "https://briefs.welance.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-welance-perfect-brief": {
      "type": "http",
      "url": "https://briefs.welance.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-welance-perfect-brief]
url = "https://briefs.welance.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-welance-perfect-brief": {
      "type": "remote",
      "url": "https://briefs.welance.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-welance-perfect-brief --url 'https://briefs.welance.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-welance-perfect-brief:
    url: "https://briefs.welance.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-welance-perfect-brief": {
      "Transport": "http",
      "Url": "https://briefs.welance.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-welance-perfect-brief -t streamable-http -u 'https://briefs.welance.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-welance-perfect-brief": {
      "type": "http",
      "url": "https://briefs.welance.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-04 (score 73, +1)

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

### 2026-11-01 (score 72, +1)

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

### 2026-10-30 (score 71, +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-10-28 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 69)

First indexed and scored.

## MCP tools (7)

### `get_rules` (~101 tokens)

Read the brief rules

Read the bar before judging anything. Free; no model runs.

    Returns the live catalogue with its version: every rule's id, title,
    criteria (what the judge reads), weight, gate role, policy context and how
    to pass it, plus the arithmetic — status scores, confidence threshold,
    accept threshold, bands, the gate and which policy contexts can be turned
    off. The number of rules is whatever the live catalogue says.

### `get_brief_template` (~65 tokens)

Get a brief template

A brief template built from the live rules, with the inputs each section needs.

    Use it to start a brief from nothing, or to see which section a gap belongs
    in. Markdown, one section per rule, gate rules marked; write in any language.

### `get_judge_prompt` (~141 tokens)

Get the judge prompt

The judge prompt and verdict JSON Schema, for YOUR model to answer. Free.

    This is the service judge's own prompt, word for word, so your model grades
    against the same bar. Pass the brief to get it embedded, or leave it empty
    for a template with a {{BRIEF}} placeholder. Answer the prompt with your
    own model (temperature 0 if you can), return only the JSON array it asks
    for, and send that array with the brief and the returned ruleset_version to
    aggregate_verdicts. welance runs no model for this.

Input parameters:

- `brief` (string)

### `get_improvement_prompt` (~111 tokens)

Get an improvement prompt

A working order for improving a brief with your own model, gate first.

    Pass the verdicts you already have (the JSON array from your model) to
    target the failing rules in weight order; without them the prompt walks
    every rule. The prompt keeps the author's voice and forbids invented
    scores and facts. Nothing is generated here: your model does the writing.

Input parameters:

- `brief` (string, required)
- `directory_context` (boolean)
- `verdicts`

### `check_brief` (~145 tokens)

Run deterministic checks

Deterministic checks only — semantic coverage is INCOMPLETE. Never a score.

    Finds what a pattern can find for certain: emails, URLs and phone numbers
    (which block anonymisation), a stated budget and timeline, personal-data
    cues without a compliance cue, unfilled placeholders, the title line and
    labelled sections. It does not judge meaning: company or person names, a
    vague problem or an unmeasurable goal pass straight through. Use it as a
    quick pre-flight, then judge with get_judge_prompt and aggregate_verdicts.

Input parameters:

- `brief` (string, required)
- `directory_context` (boolean)

### `aggregate_verdicts` (~218 tokens)

Score from your verdicts

Turn your model's verdicts into the bar's score, gate and decision. Advisory.

    Validates the verdicts against the live ruleset (every rule exactly once,
    valid status and confidence, the version you judged at) and against the
    brief (each quote must be copied verbatim), then aggregates them with the
    same engine that scores on the service: same verdicts, same number.
    Any error means no score — fix and resend.

    The result is tagged evaluation_source "client" and authoritative false:
    your model wrote the verdicts, so it is advice, never a welance score, and
    it cannot authorise publication on the welance/directory (the directory
    scores every brief itself). Say so when you report it. Fix gate.missing
    first. directory_context false drops the directory-only policy rules.

Input parameters:

- `brief` (string, required)
- `directory_context` (boolean)
- `ruleset_version` (string, required)
- `verdicts` (required)

### `bar_status` (~54 tokens)

Bar status

Which ruleset version is live, and what this free surface can do.

    Confirms the mode (bring your own model, zero provider calls, no fallback
    to welance's model) and the tools available.

## Diagnostics

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

## Score history

- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 69

## Common questions

### What is the brief bar_ MCP server?

brief bar_ is an MCP server listed in the public MCP registry as com.welance/perfect-brief. Free bar for digital product briefs: your model judges, open rules and code score it. This page covers its hosted endpoint (https://briefs.welance.com/mcp).

### Is the brief bar_ MCP server safe to use?

brief bar_ scores 73 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 brief bar_ MCP server expose?

brief bar_ exposes 7 tools: get_rules, get_brief_template, get_judge_prompt, get_improvement_prompt, check_brief, and 2 more. Their descriptions and schemas cost roughly 835 tokens of context every time the server is loaded.

### Does the brief bar_ MCP server require authentication?

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

### Is the brief bar_ MCP server still maintained?

brief bar_ 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.

## Links

- Remote endpoint: https://briefs.welance.com/mcp
- Repository: https://github.com/welance/perfect-brief
- Website: https://briefs.welance.com/integrate.html
- Changelog RSS feed: https://verifymcp.io/servers/com-welance-perfect-brief/briefs.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-welance-perfect-brief/briefs.json
- HTML version of this page: https://verifymcp.io/servers/com-welance-perfect-brief/briefs