Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

brief bar_

REMOTE · BRIEFS.WELANCE.COM

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

+3 this week 73 Trust /100

Last scanned (9 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Testing and QA

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1045 tokens (~95/item across 11 items; 7 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 4 Nov 26 +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.

  • 1 Nov 26 +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.

  • 30 Oct 26 +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.

  • 28 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 27 Oct 26 69

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://briefs.welance.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=welance.com CN=WE1,O=Google Trust Services,C=US 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA256 2d39bbf84f7223800e2a894be15272f1
SANs: welance.com, *.welance.com, *.staging.welance.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 briefs.welance.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
welance.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
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://briefs.welance.com/mcp Verified 200
http (plaintext) http://briefs.welance.com/mcp HTTPS enforced 301 https://briefs.welance.com/mcp
MCP tools · 7 exposed · ~835 tokens

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 →

Tool Tokens
aggregate_verdicts ~218

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.

NameTypeReqDescription
briefstringyes–
directory_contextboolean––
ruleset_versionstringyes–
verdicts–yes–

No output schema declared.

No examples provided.

bar_status ~54

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_brief ~145

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.

NameTypeReqDescription
briefstringyes–
directory_contextboolean––

No output schema declared.

No examples provided.

get_brief_template ~65

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_improvement_prompt ~111

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.

NameTypeReqDescription
briefstringyes–
directory_contextboolean––
verdicts–––

No output schema declared.

No examples provided.

get_judge_prompt ~141

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.

NameTypeReqDescription
briefstring––

No output schema declared.

No examples provided.

get_rules ~101

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.

remote · briefs.welance.com

# add to Claude Code
claude mcp add --transport http com-welance-perfect-brief 'https://briefs.welance.com/mcp'
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.