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

io.github.closermethod/personal-brand-mcp

NPM · PERSONAL-BRAND-MCP · SCANNED AUG 3

Positioning framework, per-platform bio auditing, 4-pillar content system, growth-signal reads.

Available components

+23 this week 65 Trust /100
Trust breakdown (6 categories)

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. How we score →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 384 tokens (~54/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 20% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · personal-brand-mcp

# add to Claude Code
claude mcp add closermethod-personal-brand-mcp -- npx -y personal-brand-mcp
# add to Codex CLI
codex mcp add closermethod-personal-brand-mcp -- npx -y personal-brand-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "closermethod-personal-brand-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "personal-brand-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add closermethod-personal-brand-mcp --command npx --arg -y --arg personal-brand-mcp
# ~/.hermes/config.yaml
mcp_servers:
  closermethod-personal-brand-mcp:
    command: "npx"
    args: ["-y", "personal-brand-mcp"]
// mcp.json
{
  "mcpServers": {
    "closermethod-personal-brand-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "personal-brand-mcp"
      ]
    }
  }
}
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.

  • 2 Aug 26 +47
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Tool coverage: 100 → unverified functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Schema quality: unverified → good functional
    • Licence: MIT functional
  • 1 Aug 26 +13
    • Tool coverage: unverified → 100 functional
  • 31 Jul 26 −37
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 42

    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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 7 exposed · ~384 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.

Tool Tokens
audit_bio ~71

Audit a profile bio: character limits per platform, hype titles vs receipts, title-first openers, missing outcome language. Platforms: tiktok, instagram, linkedin, x, youtube. Returns PASS/NEEDS WORK with a rewrite recipe.

NameTypeReqDescription
biostringyes
platformstring

No output schema declared.

No examples provided.

get_bio_rules ~48

Bio architecture per platform: what the first line must do, character priorities, CTA shape. Platforms: tiktok, instagram, linkedin, x, youtube.

NameTypeReqDescription
platformstringyes

No output schema declared.

No examples provided.

get_content_pillars ~51

The 4-pillar content system (receipts ~30%, method ~40%, story ~20%, conversion ~10%) with what each pillar does, its failure mode, and the portfolio rules.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_full_pack ~31

The complete personal-brand library in one payload: positioning, bio rules, pillars, platform strategy, signal reads.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_platform_strategy ~65

The strategic role of each platform (tiktok=reach, instagram=trust, linkedin=authority, x=network, youtube=compounding, newsletter=owned) with conversion path, cadence floor, and the watch-out.

NameTypeReqDescription
platformstringOptional: one platform

No output schema declared.

No examples provided.

get_positioning_framework ~57

The niche-statement formula (WHO x OUTCOME x HOW x RECEIPT) with the four checks, anti-patterns, the proof-inventory process, and the moat check. Positioning is upstream of every other brand decision.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

interpret_growth_signal ~61

Interpret a growth pattern: views_high_followers_flat, followers_high_engagement_low, saves_high_shares_low, dms_high_sales_low, reach_stuck_engagement_high. Returns what it means and the fix order.

NameTypeReqDescription
signalstringyes

No output schema declared.

No examples provided.