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.

comber

NPM · COMBER-MCP

Every-click AI QA: walks your whole app from a preview URL and reports broken clicks and errors.

Available components

0 this week 77 Trust /100

Last scanned (2 hours ago)

Scores higher than 55% of npm servers

Category Testing and QA

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 34 of 108 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
  • 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
  • Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 81 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 464 tokens (~154/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 3 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.

  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 +1

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

  • 1 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 19 Oct 26 0
    • Stability: 0.97 → pass security
  • 18 Oct 26 +1

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

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 5 Nov 2026 · Analysed npm/comber-mcp@0.1.4

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 108 packages
Packages resolved 108
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~464 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
comber_api_check ~164

Exercise an API surface with Comber: an OpenAPI spec, a GraphQL endpoint, or a recorded HAR. Reports contract drift, error responses, and broken operations. Read-only by default.

NameTypeReqDescription
allowPrivateTargetboolean–Target a private/staging base you own (bypasses the SSRF egress guard).
apiBasestring–Base URL for the API (required with --openapi).
graphqlstring–GraphQL endpoint URL to introspect + exercise.
harstring–Path to a recorded HAR to replay and check for drift.
openapistring–Path or URL to an OpenAPI document.
strictboolean–Return a failing summary if any 'fail' finding is present.

No output schema declared.

No examples provided.

comber_check ~239

Crawl a web app / site / SaaS surface with Comber and report broken clicks, dead ends, console errors, and broken links. Read-only by default (does not submit forms or trigger mutations). Great to run against a preview/staging URL before merging. Optional LLM finding-judge only runs if ANTHROPIC_API_KEY is set in the environment.

NameTypeReqDescription
allowWritesboolean–DANGER: exercise mutating controls/methods (submits, deletes). Off by default. Only enable against a disposable target you own.
crossOriginboolean–Follow links off the start origin. Default: same-origin only.
externalLinksboolean–Verify external links (HEAD/GET). Default: off.
maxActionsinteger–Cap on total actions taken (runaway-cost backstop).
maxStatesinteger–Cap on distinct app states to explore (runaway-cost backstop).
strictboolean–Return a failing summary if any 'fail' finding is present (gate a merge).
urlstringyesThe URL to crawl (e.g. a preview deployment).

No output schema declared.

No examples provided.

comber_report ~61

Read the full findings list from a previous comber run. Pass the runDir returned by comber_check / comber_api_check.

NameTypeReqDescription
runDirstringyesThe runDir path returned by a prior comber_check / comber_api_check call.

No output schema declared.

No examples provided.

Install

How do I install the comber MCP server?

comber runs locally as an npm package, launched with npx -y comber-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 · comber-mcp

# add to Claude Code
claude mcp add io-codecomber-comber -- npx -y comber-mcp
Common questions

What is the comber MCP server?

comber is an MCP server listed in the public MCP registry as io.codecomber/comber. Every-click AI QA: walks your whole app from a preview URL and reports broken clicks and errors. This page covers its npm package (comber-mcp).

Is the comber MCP server safe to use?

comber scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 comber MCP server expose?

comber exposes 3 tools: comber_check, comber_api_check, comber_report. Their descriptions and schemas cost roughly 464 tokens of context every time the server is loaded.

Is the comber MCP server still maintained?

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