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.

Unchore Defend

MCPB · UNCHORE-DEFEND.MCPB

Grade a site's security headers with fixes and a badge; read logs or code for the defender.

+9 this week 54 Trust /100

Last scanned (14 hours ago)

Scores higher than 91% of MCPB servers

Category Security

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 Security13
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • No install/post-install scripts declared.Pass
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
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 Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 238 tokens (~119/item across 2 items; 2 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 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.

  • 18 Oct 26 +1

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

  • 16 Oct 26 +1

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

  • 14 Oct 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.

  • 13 Oct 26 +6
    • Stability: unverified → 0.43 ▲ functional
  • 30 Sept 26 45

    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 18 Oct 2026 · Analysed mcpb/https://github.com/smilemino/unchore-defend/releases/download/v0.1.0/unchore-defend.mcpb

Provenance No attestation

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

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 2 exposed · ~211 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
defend_analyze ~147

Read a log, code, config or suspicious message and say what happened, how bad it is and what to fix first. Personal data and secrets are masked before sending. If one AI refuses, the next answers (Claude → GPT → GLM → DeepSeek). Needs UNCHORE_TOKEN or OPENROUTER_API_KEY.

NameTypeReqDescription
chainstring–Order of AIs, e.g. 'claude,gpt,glm,deepseek' (optional)
evidencestring–Log lines, code or the message to analyse (optional)
questionstringyesThe question in plain words, e.g. 'Who got in and what did they take?'

No output schema declared.

No examples provided.

site_check ~64

Grade a public website's security headers and cookie flags (A–F, 0–100) with the one-line fix for each gap and a README badge. Sends one GET to the site only.

NameTypeReqDescription
urlstringyesSite address, e.g. example.com

No output schema declared.

No examples provided.

Install

How do I install the Unchore Defend MCP server?

Unchore Defend ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 302a753ed7471077bbf76cfbda6806d01ad1ffd2f97f49deab664bed02664785; the commands to do that are on this page. If it does not match, do not open it.

mcpb · unchore-defend.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

302a753ed7471077bbf76cfbda6806d01ad1ffd2f97f49deab664bed02664785

macOS / Linux

echo "302a753ed7471077bbf76cfbda6806d01ad1ffd2f97f49deab664bed02664785  unchore-defend.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\unchore-defend.mcpb).Hash -eq "302a753ed7471077bbf76cfbda6806d01ad1ffd2f97f49deab664bed02664785"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the Unchore Defend MCP server?

Unchore Defend is an MCP server listed in the public MCP registry as io.github.smilemino/unchore-defend. Grade a site's security headers with fixes and a badge; read logs or code for the defender. This page covers its MCPB bundle (https://github.com/smilemino/unchore-defend/releases/download/v0.1.0/unchore-defend.mcpb).

Is the Unchore Defend MCP server safe to use?

Unchore Defend scores 54 out of 100 on VerifyMCP. 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 Unchore Defend MCP server expose?

Unchore Defend exposes 2 tools: site_check, defend_analyze. Their descriptions and schemas cost roughly 211 tokens of context every time the server is loaded.

What licence is the Unchore Defend MCP server under?

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