brief bar_
com.welance/perfect-briefwelance.comstreamable-httpv1.14.1Scanned
Free bar for digital product briefs: your model judges, open rules and code score it.
7 tools: 2 change things and 5 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 2Claude Code: ask
aggregate_verdictsTurn your model's verdicts into the bar's score, gate and decision.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
check_briefDeterministic checks only — semantic coverage is INCOMPLETE.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
Only reads 5Show 5 read-only tools
bar_statusWhich ruleset version is live, and what this free surface can do.No findings
Why it is in this group
- The name "bar_status" says "status": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_brief_templateA brief template built from the live rules, with the inputs each section needs.No findings
Why it is in this group
- The name "get_brief_template" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_improvement_promptA working order for improving a brief with your own model, gate first.Reads private dataNo findings
Why it is in this group
- The name "get_improvement_prompt" says "get": a word for reading.
What it can reach
- private-dataThe input names a directory (input.directory_context), and the tool reads: it reads files.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_judge_promptThe judge prompt and verdict JSON Schema, for YOUR model to answer.No findings
Why it is in this group
- The name "get_judge_prompt" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_rulesRead the bar before judging anything.No findings
Why it is in this group
- The name "get_rules" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.14.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http perfect-brief https://briefs.welance.com/mcpclaude mcp add --transport http perfect-brief https://briefs.welance.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__perfect-brief__get_rules",
"mcp__perfect-brief__get_brief_template",
"mcp__perfect-brief__get_judge_prompt",
"mcp__perfect-brief__get_improvement_prompt",
"mcp__perfect-brief__bar_status"
],
"ask": [
"mcp__perfect-brief__check_brief",
"mcp__perfect-brief__aggregate_verdicts"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as perfect-brief. Review it before you use it.
Capability tags behind 1 rule
- mcp__perfect-brief__get_improvement_prompt private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/com.welance/perfect-brief/verify?hash=f314eaca88967e6d65592482c09b8906e52b571f26f8afbde3bfe1d00ab3d5bf" | jq -e '.changed == false'Pinned hash f314eaca8896, from Oct 27, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/com.welance/perfect-brief/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/com.welance/perfect-brief)Source: MCP Registry · repository. Synced Oct 27, 2026, 16:17 UTC.