rea-captcha
NPM · REA-CAPTCHA
Safe same-session CAPTCHA handoff and fresh-evidence resume for Browser Use and Playwright agents.
Available components
Last scanned (5 hours ago)
Scores higher than 58% of npm servers
Category Browser Automation
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 Security98
- 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
- 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to masakaai/rea-captcha). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 446 tokens (~74/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: the tool surface changed between 0.2.4 and 0.3.1: 0 tool removals, 1 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 53% 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 6 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 17 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 16 Oct 26 +15
- Stability: unverified → fail ▼ security
- Tool safety: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- 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. security
- Schema quality: 62 → 74 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Tool coverage: 43% → 53% ▲ functional
- Dependency health: unverified → 0.85 ▲ functional
- Package version: 0.2.4 → 0.3.1 functional
- Package version: 0.2.4 → 0.3.0 functional
- 15 Oct 26 +13
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- 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). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 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 functional
- 14 Oct 26 39
First indexed and scored.
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 17 Oct 2026 · Analysed npm/rea-captcha@0.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | masakaai/rea-captcha |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/masakaai/rea-captcha/.github/workflows/publish-npm.yml@refs/tags/v0.3.1 |
| Rekor log index | 3279024449 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:047ea7d530dd2b44f2ce2b8a689bb98b6721eb66ff2cbfa4372e3178f436b146d7223c213a2f3d7607f0506178edc624c2fdc4858483e7483724d6adc |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
captcha_analyze Analyze page evidence ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | – | – |
| runtime_signals | array | – | – |
| text | string | – | – |
| title | string | – | – |
| url | string | yes | URL of the page observed by the calling agent. |
No output schema declared.
No examples provided.
captcha_complete Complete authorized verification ~64
Let the agent complete an authorized provider-test or owned-origin challenge in the existing browser session, then wait for fresh server-validated evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| poll_ms | integer | – | – |
| session_id | string | yes | Configured browser session identifier. |
| timeout_ms | integer | – | – |
No output schema declared.
No examples provided.
captcha_handoff Request human handoff ~64
Bind the current challenge to a caller-owned task and create a generation-scoped human handoff in the existing browser session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Configured browser session identifier. |
| task_id | string | yes | Caller-owned task or run identifier for this handoff. |
No output schema declared.
No examples provided.
captcha_inspect Inspect verification challenge ~40
Inspect a configured browser session for an active verification challenge and return evidence plus the handling policy.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Configured browser session identifier. |
No output schema declared.
No examples provided.
captcha_resume Verify and resume ~82
Consume the matching task-scoped handoff once, re-inspect the existing browser session, and resume only after the current challenge is clear.
| Name | Type | Req | Description |
|---|---|---|---|
| handoff_id | string | – | Opaque identifier returned by captcha_handoff. |
| session_id | string | yes | Configured browser session identifier. |
| task_id | string | – | Task identifier used for a human handoff. |
No output schema declared.
No examples provided.
captcha_wait Wait for verification ~53
Poll the same browser session until its verification challenge clears or the bounded timeout expires.
| Name | Type | Req | Description |
|---|---|---|---|
| poll_ms | integer | – | – |
| session_id | string | yes | Configured browser session identifier. |
| timeout_ms | integer | – | – |
No output schema declared.
No examples provided.
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.
npm · rea-captcha
claude mcp add masakaai-rea-captcha -- npx -y rea-captcha
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.