NoneCap
NPM · NONECAP
Solve hCaptcha and hCaptcha Enterprise challenges and get back a token, via the NoneCap API.
Available components
Last scanned (8 hours ago)
Scores higher than 77% of npm servers
Category Security
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to nonecap/nonecap-js). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 576 tokens (~96/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 Management13
- Stability observed for 4 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 81
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 5 Nov 2026 · Analysed npm/nonecap@0.13.0
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 | nonecap/nonecap-js |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/nonecap/nonecap-js/.github/workflows/ci.yml@refs/tags/v0.13.0 |
| Rekor log index | 3635461650 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:881ccaa76b498a92129d7f84ff9146b0cfd896896f65701caffa350a1ae73979170792770963c7dc139de39f0e1f81d32e1c99c0ac3d2c3faa1a04131 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
cancel_solve Cancel a solve ~37
Cancel a pending or running solve. Cancelled solves are not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The solve id (solve_…). |
No output schema declared.
No examples provided.
get_account Get account ~25
Get your NoneCap account: credit balance, and your plan's solves left today.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_solve Get a solve ~81
Get a solve by id: its status, and the token once it is solved. Set wait_seconds to wait for it to finish.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 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. |
No output schema declared.
No examples provided.
list_solves List solves ~84
List your recent solves, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
report_solve_outcome Report a token's outcome ~119
Tell NoneCap whether the site accepted a solve's token. Free; reporting the same solve again corrects it.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Anything else about the attempt that would help diagnose it. |
| outcome | string | yes | 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 | yes | The id of a solved solve. |
No output schema declared.
No examples provided.
solve_hcaptcha Solve an hCaptcha ~230
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The hCaptcha sitekey on the page. |
| type | string | – | hcaptcha (default) or hcaptcha_enterprise. |
| url | string | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · nonecap
claude mcp add nonecap-nonecap -- npx -y nonecap
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.