# io.github.closermethod/ugc-brief-mcp (npm · ugc-brief-mcp)

Turn a brand brief into deliverables, shot lists, and the right UGC format, catching scope traps.

- Trust score: 65/100 (medium)
- Change this week: +41
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- npm · `ugc-brief-mcp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/closermethod-ugc-brief-mcp/ugc-brief-mcp.md), [page](https://verifymcp.io/servers/closermethod-ugc-brief-mcp/ugc-brief-mcp)

## Channel facts

- Registry: `npm`
- Package: `ugc-brief-mcp`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-08-04.

- **Supply Chain Security**: 83/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 410 tokens (~58/item across 7 items; 7 tools + 0 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**: 75/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 25% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add closermethod-ugc-brief-mcp -- npx -y ugc-brief-mcp
```

### Codex

```bash
codex mcp add closermethod-ugc-brief-mcp -- npx -y ugc-brief-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "closermethod-ugc-brief-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "ugc-brief-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add closermethod-ugc-brief-mcp --command npx --arg -y --arg ugc-brief-mcp
```

### Hermes

```yaml
mcp_servers:
  closermethod-ugc-brief-mcp:
    command: "npx"
    args: ["-y", "ugc-brief-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "closermethod-ugc-brief-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ugc-brief-mcp"
      ]
    }
  }
}
```

## 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-08-04 (score 65, −1)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail

### 2026-08-03 (score 66, +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-08-02 (score 65, +60)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] License: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] Schema quality: unverified → good
- [functional improvement] Dependency health: unverified → partial
- [functional] Licence: MIT

### 2026-08-01 (score 5, −20)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 25, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-30 (score 43, +19)

- [functional improvement] Tool coverage: unverified → 100

### 2026-07-28 (score 24, −19)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 43)

First indexed and scored.

## MCP tools (7)

### `interpret_brief` (~68 tokens)

Paste a brand's UGC brief. Returns detected deliverables/specs/usage/disclosure, red flags (unlimited revisions, perpetual usage, spec work, raw-file grabs), and the exact questions to confirm in writing before agreeing.

Input parameters:

- `brief` (string, required): The full brand brief text

### `get_brief_checklist` (~54 tokens)

The 10-point checklist every UGC brief must answer before you shoot: deliverables, usage, exclusivity, revisions, raw-vs-edited, specs, hooks, talking points, timeline, brand assets.

### `get_ugc_formats` (~60 tokens)

The core UGC ad formats with structure and when to use each: testimonial, problem_solution, unboxing, demo_tutorial, get_ready_with_me, comparison, hook_test_pack. Omit format for all.

Input parameters:

- `format` (string)

### `build_shot_list` (~79 tokens)

Given a UGC format, returns a beat-by-beat shot list template with coverage rules (shoot the hook 3 ways, get product close-up + in-use wide + reaction). Formats: testimonial, problem_solution, unboxing, demo_tutorial, get_ready_with_me, comparison, hook_test_pack.

Input parameters:

- `format` (string, required)

### `scope_deliverables` (~55 tokens)

Turn a vague ask into a defined deliverable list. Returns the exact fields to lock (count, format, length, aspect, revisions, raw-vs-edited, usage window) so nothing is left open to interpretation.

### `check_brief_red_flags` (~61 tokens)

Scan a brief or message for production/scope red flags: unlimited revisions, perpetual usage, spec-first requests, raw-file grabs, vague deliverables, post-agreement scope creep. Returns flags + what to do.

Input parameters:

- `text` (string, required)

### `get_full_pack` (~33 tokens)

The complete UGC-brief library in one payload: formats, brief checklist, red flags. For full agent context.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/closermethod-ugc-brief-mcp/ugc-brief-mcp#diagnostics

## Score history

- 2026-08-04: 65
- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 5
- 2026-07-31: 25
- 2026-07-30: 43
- 2026-07-28: 24
- 2026-07-27: 43

## Links

- npm package: https://www.npmjs.com/package/ugc-brief-mcp
- Socket report: https://socket.dev/npm/package/ugc-brief-mcp
- Repository: https://github.com/closermethod/ugc-brief-mcp
- Changelog RSS feed: https://verifymcp.io/servers/closermethod-ugc-brief-mcp/ugc-brief-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/closermethod-ugc-brief-mcp/ugc-brief-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/closermethod-ugc-brief-mcp/ugc-brief-mcp