nokk
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOKK_PROXY | No | Upstream proxy, e.g. socks5://host:1080 | |
| NOKK_NO_AUTO_SOLVE | No | 1: do not solve challenges during navigation | |
| NOKK_ROTATE_FINGERPRINT | No | 1: each session gets its own coherent fingerprint |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| openA | Navigate the stealth browser to A Cloudflare challenge on the way is solved before this returns (unless the
server runs with |
| solve_challengeA | 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 |
| challenge_stateA | Which gate the current page shows: |
| read_textA | Visible text of the current page, or of the first element matching the CSS
|
| read_htmlA | Outer HTML of the current page, or of the first element matching the CSS
|
| clickC | Click the first element matching the CSS |
| fillB | Set the value of the form field matching |
| evaluateC | Evaluate a JavaScript expression in the current page and return its value. |
| linksB | All absolute hyperlink URLs on the current page. |
| resetA | Discard the current browsing session (a fresh, coherent identity is used for the next navigation). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool maps to a distinct action on the browser session: navigate (open), interact (click/fill), read (read_text/read_html/links), execute JS (evaluate), and Cloudflare handling (solve_challenge vs challenge_state, one acting and one querying). The only mild overlap is that `open` can auto-solve challenges while `solve_challenge` does so manually, but the description explicitly flags this and reports the challenge outcome, so an agent can tell them apart.
Names are uniformly short, lowercase snake_case, with related tools grouped by prefix (read_text/read_html, challenge_state/solve_challenge). Some tools are bare verbs (open, click, fill, evaluate) and one is a bare noun (links), so it is not a strict verb_noun pattern throughout, but the convention is predictable and readable.
Ten tools is well-scoped for a stealth browser driver: navigation, two readers, two interaction primitives, JS evaluation, link extraction, challenge state/solve, and session reset. Nothing looks redundant or padded.
The core browse-inspect-interact lifecycle plus Cloudflare bypass and session reset is covered, but there is no wait-for-element, screenshot, keyboard press/Enter, select-option, or history navigation tool. Most of these gaps are workaroundable via `evaluate` and `click`/`fill`, so they are minor rather than blocking.