# NoneCap (npm · nonecap)

Solve hCaptcha and hCaptcha Enterprise challenges and get back a token, via the NoneCap API.

- Trust score: 83/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `nonecap`: 83/100 (this document), [markdown](https://verifymcp.io/servers/nonecap-nonecap/nonecap.md), [page](https://verifymcp.io/servers/nonecap-nonecap/nonecap)

## Channel facts

- Registry: `npm`
- Package: `nonecap`
- Version: `0.13.0`
- 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-11-05.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to nonecap/nonecap-js).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 576 tokens (~96/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 6 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 NoneCap MCP server?

NoneCap runs locally as an npm package, launched with npx -y nonecap. 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 nonecap-nonecap -- npx -y nonecap
```

### Cursor

```json
{
  "mcpServers": {
    "nonecap-nonecap": {
      "command": "npx",
      "args": [
        "-y",
        "nonecap"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nonecap-nonecap": {
      "command": "npx",
      "args": [
        "-y",
        "nonecap"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add nonecap-nonecap -- npx -y nonecap
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add nonecap-nonecap --command npx --arg -y --arg nonecap
```

### Hermes

```yaml
mcp_servers:
  nonecap-nonecap:
    command: "npx"
    args: ["-y", "nonecap"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add nonecap-nonecap -t stdio -c npx -a -y nonecap
```

### Other

```json
{
  "mcpServers": {
    "nonecap-nonecap": {
      "command": "npx",
      "args": [
        "-y",
        "nonecap"
      ]
    }
  }
}
```

## 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-11-05 (score 83, +1)

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

### 2026-11-03 (score 82, +1)

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

### 2026-11-01 (score 81)

First indexed and scored.

## MCP tools (6)

### `solve_hcaptcha` (~230 tokens)

Solve an hCaptcha

Solve an hCaptcha and return the token. Waits up to wait_seconds; if the solve is still running then, returns its id and status: call get_solve with the id rather than solving again. Only successful solves are charged.

Input parameters:

- `proxy` (string): Proxy to solve through, as a URL: scheme://user:pass@host:port (http, https, socks5, socks5h or socks4).
- `rqdata` (string): Enterprise only: the rqdata the site passes to its widget, if it passes one.
- `sitekey` (string, required): The hCaptcha sitekey on the page.
- `type` (string): hcaptcha (default) or hcaptcha_enterprise.
- `url` (string, required): The URL of the page the captcha is on.
- `user_agent` (string): The user agent of the browser that loaded the page, as is. Leave out if you do not have it.
- `wait_seconds` (integer): Seconds to wait for the result, 0-50. Default 45. 0 returns right after submitting.

### `get_solve` (~81 tokens)

Get a solve

Get a solve by id: its status, and the token once it is solved. Set wait_seconds to wait for it to finish.

Input parameters:

- `id` (string, required): The solve id (solve_…).
- `wait_seconds` (integer): Hold up to this many seconds (1-50) for the solve to finish. Omit to return at once.

### `cancel_solve` (~37 tokens)

Cancel a solve

Cancel a pending or running solve. Cancelled solves are not charged.

Input parameters:

- `id` (string, required): The solve id (solve_…).

### `list_solves` (~84 tokens)

List solves

List your recent solves, newest first.

Input parameters:

- `limit` (integer): Page size, 1-100. Default 20.
- `starting_after` (string): A solve id: return the page after it (the last id of the previous page).
- `status` (string): Only solves with this status.
- `type` (string): Only solves of this type.

### `get_account` (~25 tokens)

Get account

Get your NoneCap account: credit balance, and your plan's solves left today.

### `report_solve_outcome` (~119 tokens)

Report a token's outcome

Tell NoneCap whether the site accepted a solve's token. Free; reporting the same solve again corrects it.

Input parameters:

- `context` (string): Anything else about the attempt that would help diagnose it.
- `outcome` (string, required): accepted or rejected by the site; unknown (submitted, verdict unclear); unused (never submitted); error (the site failed for a reason unrelated to the token).
- `reason` (string): What the site returned when it refused the token.
- `solve_id` (string, required): The id of a solved solve.

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81

## Common questions

### What is the NoneCap MCP server?

NoneCap is an MCP server listed in the public MCP registry as io.github.nonecap/nonecap. Solve hCaptcha and hCaptcha Enterprise challenges and get back a token, via the NoneCap API. This page covers its npm package (nonecap).

### Is the NoneCap MCP server safe to use?

NoneCap scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 NoneCap MCP server expose?

NoneCap exposes 6 tools: solve_hcaptcha, get_solve, cancel_solve, list_solves, get_account, report_solve_outcome. Their descriptions and schemas cost roughly 576 tokens of context every time the server is loaded.

### Is the NoneCap MCP server still maintained?

NoneCap 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.

### What licence is the NoneCap MCP server under?

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

### What did VerifyMCP test on the NoneCap MCP server?

VerifyMCP ran 16 checks on NoneCap, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/nonecap
- Socket report: https://socket.dev/npm/package/nonecap
- Repository: https://github.com/nonecap/nonecap-js
- Website: https://nonecap.com/
- Changelog RSS feed: https://verifymcp.io/servers/nonecap-nonecap/nonecap.xml
- Changelog JSON feed: https://verifymcp.io/servers/nonecap-nonecap/nonecap/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/nonecap-nonecap/nonecap.json
- HTML version of this page: https://verifymcp.io/servers/nonecap-nonecap/nonecap