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.

nokk

PYPI · NOKK-MCP

Headless browser for AI agents with Chrome's fingerprint that passes Cloudflare challenges.

Available components

+4 this week 67 Trust /100

Last scanned (1 hour ago)

Scores higher than 64% of PyPI servers

Category Browser Automation

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to koloss777/nokk). View diagnostics → Pass
  • Clear OSI-approved license (MIT OR Apache-2.0).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 461 tokens (~46/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (90% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 1 Nov 26 +1

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

  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 +1

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

  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 27 Oct 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.

  • 25 Oct 26 77

    First indexed and scored.

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 pypi/nokk-mcp@0.1.46a1

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo koloss777/nokk
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/koloss777/nokk/.github/workflows/python-wheels.yml@refs/tags/v0.1.46-alpha
Rekor log index 3456784406
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:9035f3567c49624599a24f908104f0a29940d765f9df295b2925ab1d9da725de

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 30 packages
Packages resolved 30
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~461 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
challenge_state ~87

Which gate the current page shows: ``kind`` is ``"none"``, ``"cloudflare-interstitial"``, ``"turnstile-widget"``, ``"aws-waf"``, ``"recaptcha-widget"`` or ``"datadome"`` (recognised, not solvable); ``solvable`` says whether ``solve_challenge`` can take it on.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultobjectyes–

No examples provided.

click ~25

Click the first element matching the CSS ``selector``.

NameTypeReqDescription
selectorstringyes–
NameTypeReqDescription
resultbooleanyes–

No examples provided.

evaluate ~28

Evaluate a JavaScript expression in the current page and return its value.

NameTypeReqDescription
expressionstringyes–

No output schema declared.

No examples provided.

fill ~37

Set the value of the form field matching ``selector`` and fire input/change.

NameTypeReqDescription
selectorstringyes–
valuestringyes–
NameTypeReqDescription
resultbooleanyes–

No examples provided.

links ~16

All absolute hyperlink URLs on the current page.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

open ~92

Navigate the stealth browser to ``url``. Returns the final ``{url, title}``. A Cloudflare challenge on the way is solved before this returns (unless the server runs with ``--no-auto-solve``); ``challenge`` then reports what was met: ``kind``, ``solved``, and ``remaining`` (``"none"`` when through).

NameTypeReqDescription
urlstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

read_html ~37

Outer HTML of the current page, or of the first element matching the CSS ``selector`` if given.

NameTypeReqDescription
selectorstring––
NameTypeReqDescription
result–yes–

No examples provided.

read_text ~37

Visible text of the current page, or of the first element matching the CSS ``selector`` if given.

NameTypeReqDescription
selectorstring––
NameTypeReqDescription
result–yes–

No examples provided.

reset ~27

Discard the current browsing session (a fresh, coherent identity is used for the next navigation).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

solve_challenge ~75

Solve the Cloudflare challenge the current page shows — the "Just a moment…" interstitial or a Turnstile widget — pressing its checkbox if it puts one up. Returns ``status``, ``solved``, ``remaining``, ``title``, ``url``.

NameTypeReqDescription
timeout_secondsnumber––
NameTypeReqDescription
resultobjectyes–

No examples provided.

Install

How do I install the nokk MCP server?

nokk runs locally as a PyPI package, launched with uvx nokk-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · nokk-mcp

# add to Claude Code
claude mcp add koloss777-nokk -- uvx nokk-mcp
Common questions

What is the nokk MCP server?

nokk is an MCP server listed in the public MCP registry as io.github.koloss777/nokk. Headless browser for AI agents with Chrome's fingerprint that passes Cloudflare challenges. This page covers its PyPI package (nokk-mcp).

Is the nokk MCP server safe to use?

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

nokk exposes 10 tools: open, solve_challenge, challenge_state, read_text, read_html, and 5 more. Their descriptions and schemas cost roughly 461 tokens of context every time the server is loaded.

Is the nokk MCP server still maintained?

nokk 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 nokk MCP server under?

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