# rea-captcha (npm · rea-captcha)

Safe same-session CAPTCHA handoff and fresh-evidence resume for Browser Use and Playwright agents.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- npm · `rea-captcha`: 78/100 (this document), [markdown](https://verifymcp.io/servers/masakaai-rea-captcha/rea-captcha.md), [page](https://verifymcp.io/servers/masakaai-rea-captcha/rea-captcha)

## Channel facts

- Registry: `npm`
- Package: `rea-captcha`
- Version: `0.3.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-10-17.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 94 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to masakaai/rea-captcha).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 446 tokens (~74/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: the tool surface changed between 0.2.4 and 0.3.1: 0 tool removals, 1 breaking changes, 0 additions.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 53% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the rea-captcha MCP server?

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

### Claude

```bash
claude mcp add masakaai-rea-captcha -- npx -y rea-captcha
```

### Cursor

```json
{
  "mcpServers": {
    "masakaai-rea-captcha": {
      "command": "npx",
      "args": [
        "-y",
        "rea-captcha"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "masakaai-rea-captcha": {
      "command": "npx",
      "args": [
        "-y",
        "rea-captcha"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add masakaai-rea-captcha -- npx -y rea-captcha
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add masakaai-rea-captcha --command npx --arg -y --arg rea-captcha
```

### Hermes

```yaml
mcp_servers:
  masakaai-rea-captcha:
    command: "npx"
    args: ["-y", "rea-captcha"]
```

### Netclaw

```json
{
  "McpServers": {
    "masakaai-rea-captcha": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "rea-captcha"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add masakaai-rea-captcha -t stdio -c npx -a -y rea-captcha
```

### Other

```json
{
  "mcpServers": {
    "masakaai-rea-captcha": {
      "command": "npx",
      "args": [
        "-y",
        "rea-captcha"
      ]
    }
  }
}
```

## 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-10-17 (score 78, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

### 2026-10-16 (score 67, +15)

- [security regression] Stability: unverified → fail
- [security regression] Tool safety: pass → unverified
- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Schema quality: 62 → 74
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Tool coverage: 43% → 53%
- [functional improvement] Dependency health: unverified → 0.85
- [functional] Package version: 0.2.4 → 0.3.1
- [functional] Package version: 0.2.4 → 0.3.0

### 2026-10-15 (score 52, +13)

- [security regression] Malware scan: pass → unverified
- [security improvement] Injection markers: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Tool coverage: 43
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] Package version: 0.2.1 → 0.2.4
- [functional] Package version: 0.2.1 → 0.2.3

### 2026-10-14 (score 39)

First indexed and scored.

## MCP tools (6)

### `captcha_inspect` (~40 tokens)

Inspect verification challenge

Inspect a configured browser session for an active verification challenge and return evidence plus the handling policy.

Input parameters:

- `session_id` (string, required): Configured browser session identifier.

### `captcha_complete` (~64 tokens)

Complete authorized verification

Let the agent complete an authorized provider-test or owned-origin challenge in the existing browser session, then wait for fresh server-validated evidence.

Input parameters:

- `poll_ms` (integer)
- `session_id` (string, required): Configured browser session identifier.
- `timeout_ms` (integer)

### `captcha_wait` (~53 tokens)

Wait for verification

Poll the same browser session until its verification challenge clears or the bounded timeout expires.

Input parameters:

- `poll_ms` (integer)
- `session_id` (string, required): Configured browser session identifier.
- `timeout_ms` (integer)

### `captcha_handoff` (~64 tokens)

Request human handoff

Bind the current challenge to a caller-owned task and create a generation-scoped human handoff in the existing browser session.

Input parameters:

- `session_id` (string, required): Configured browser session identifier.
- `task_id` (string, required): Caller-owned task or run identifier for this handoff.

### `captcha_resume` (~82 tokens)

Verify and resume

Consume the matching task-scoped handoff once, re-inspect the existing browser session, and resume only after the current challenge is clear.

Input parameters:

- `handoff_id` (string): Opaque identifier returned by captcha_handoff.
- `session_id` (string, required): Configured browser session identifier.
- `task_id` (string): Task identifier used for a human handoff.

### `captcha_analyze` (~93 tokens)

Analyze page evidence

Analyze URL, title, HTML, text, or runtime signals already available to the calling agent. This read-only tool needs no configured browser adapter and does not control or preserve a browser session.

Input parameters:

- `html` (string)
- `runtime_signals` (array)
- `text` (string)
- `title` (string)
- `url` (string, required): URL of the page observed by the calling agent.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/masakaai-rea-captcha/rea-captcha#diagnostics

## Score history

- 2026-10-17: 78
- 2026-10-16: 67
- 2026-10-15: 52
- 2026-10-14: 39

## Common questions

### What is the rea-captcha MCP server?

rea-captcha is an MCP server listed in the public MCP registry as io.github.masakaai/rea-captcha. Safe same-session CAPTCHA handoff and fresh-evidence resume for Browser Use and Playwright agents. This page covers its npm package (rea-captcha).

### Is the rea-captcha MCP server safe to use?

rea-captcha scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 rea-captcha MCP server expose?

rea-captcha exposes 6 tools: captcha_inspect, captcha_complete, captcha_wait, captcha_handoff, captcha_resume, captcha_analyze. Their descriptions and schemas cost roughly 396 tokens of context every time the server is loaded.

### Is the rea-captcha MCP server still maintained?

rea-captcha is still listed as active in the MCP registry. We last reached this channel on 17 October 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 rea-captcha MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/rea-captcha
- Socket report: https://socket.dev/npm/package/rea-captcha
- Repository: https://github.com/masakaai/rea-captcha
- Changelog RSS feed: https://verifymcp.io/servers/masakaai-rea-captcha/rea-captcha.xml
- Changelog JSON feed: https://verifymcp.io/servers/masakaai-rea-captcha/rea-captcha.json
- HTML version of this page: https://verifymcp.io/servers/masakaai-rea-captcha/rea-captcha