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.

WrapGuard MCP

NPM · WRAPGUARD-MCP · SCANNED SEP 20

Detect unnatural Korean and English mid-word wrapping in responsive web pages.

Available components

+3 this week 73 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 7 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 17 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability54
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 440 tokens (~62/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 Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 11% of tool parameters carry a description.Partial
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 7 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
Install

How do I install the WrapGuard MCP server?

WrapGuard MCP runs locally as an npm package, launched with npx -y wrapguard-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · wrapguard-mcp

# add to Claude Code
claude mcp add yuni9959-wrapguard-mcp -- npx -y wrapguard-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "yuni9959-wrapguard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "wrapguard-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "yuni9959-wrapguard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "wrapguard-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add yuni9959-wrapguard-mcp -- npx -y wrapguard-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yuni9959-wrapguard-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "wrapguard-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add yuni9959-wrapguard-mcp --command npx --arg -y --arg wrapguard-mcp
# ~/.hermes/config.yaml
mcp_servers:
  yuni9959-wrapguard-mcp:
    command: "npx"
    args: ["-y", "wrapguard-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "yuni9959-wrapguard-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "wrapguard-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add yuni9959-wrapguard-mcp -t stdio -c npx -a -y wrapguard-mcp
// mcp.json
{
  "mcpServers": {
    "yuni9959-wrapguard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "wrapguard-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.

  • 19 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 10 Sept 26 +4
    • Stability: unverified → 0.27 functional
  • 3 Sept 26 +15
    • Malware scan: unverified → pass security
  • 2 Sept 26 50

    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 20 Sept 2026 · Analysed npm/wrapguard-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 7 packages
Packages resolved 7
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~440 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
apply_wrap_fix ~63

Append an idempotent CSS rule. Dry-run is the default; real writes require allowWrites and an allowed root.

NameTypeReqDescription
cssFilestringyes
dryRunboolean
profilestringyes
selectorstringyes

No output schema declared.

No examples provided.

audit_page ~81

Render a page at multiple widths and report Korean/English mid-word wraps and forced source newlines.

NameTypeReqDescription
ignoreSelectorsarray
localestring
screenshotDirstring
targetstringyesAllowed local HTML path, file URL, or allowlisted HTTP(S) URL
viewportsarray

No output schema declared.

No examples provided.

detect_midword_breaks ~81

Return only concrete Korean/English wrap issues measured from grapheme geometry in the browser.

NameTypeReqDescription
ignoreSelectorsarray
localestring
screenshotDirstring
targetstringyesAllowed local HTML path, file URL, or allowlisted HTTP(S) URL
viewportsarray

No output schema declared.

No examples provided.

inspect_wrap_css ~44

Inspect computed wrapping properties and same-origin matching CSS rules for one element.

NameTypeReqDescription
selectorstringyes
targetstringyes
viewportinteger

No output schema declared.

No examples provided.

server_info ~21

Show the configured display name, safety policy, and supported languages.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

suggest_wrap_fix ~53

Generate a minimal CSS rule for Korean, English, mixed prose, raw evidence, or code/URL content.

NameTypeReqDescription
contentKindstring
localestring
selectorstringyes

No output schema declared.

No examples provided.

verify_wrap_regression ~97

Audit a page and evaluate it against explicit error/warning thresholds for CI or release gates.

NameTypeReqDescription
ignoreSelectorsarray
localestring
maxErrorsinteger
maxWarningsinteger
screenshotDirstring
targetstringyesAllowed local HTML path, file URL, or allowlisted HTTP(S) URL
viewportsarray

No output schema declared.

No examples provided.

Common questions

What is the WrapGuard MCP server?

WrapGuard MCP is listed in the public MCP registry as io.github.Yuni9959/wrapguard-mcp. Detect unnatural Korean and English mid-word wrapping in responsive web pages. This page covers its npm package (wrapguard-mcp).

Is the WrapGuard MCP server safe to use?

WrapGuard MCP scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 WrapGuard MCP server expose?

WrapGuard MCP exposes 7 tools: server_info, audit_page, detect_midword_breaks, inspect_wrap_css, suggest_wrap_fix, and 2 more. Their descriptions and schemas cost roughly 440 tokens of context every time the server is loaded.

Is the WrapGuard MCP server still maintained?

WrapGuard MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the WrapGuard MCP server under?

WrapGuard MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.