Wraith MCP Server

Overview Schema Source Related Servers Discussions Admin

navigate

Opens a URL and returns an indexed snapshot of interactive page elements, automatically handling WAAP challenges and cookie/consent banners.

Instructions

Open a URL and return an indexed snapshot of the page's interactive elements.

Automatically attempts WAAP challenges, including HUMAN/PerimeterX Press & Hold, and dismisses common cookie/consent banners. No separate challenge command is needed. If verification fails, navigation reports an error; do not assume clearance. Set require_clearance=true on Akamai: a clean 200 does not count, so it waits for a valid clearance cookie (_abck can be present but unsolved). Each line is [index]<tag role=...>text</tag>; use the index with click / type_text. Pass include_snapshot=false for a compact summary (saves tokens; call snapshot() when you need the list).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "navigate"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`include_snapshot`	No
`require_clearance`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.21.0Oct 30, 2026

addedInput schema / properties / require_clearance

Added value: +{
+  "default": false,
+  "title": "Require Clearance",
+  "type": "boolean"
+}

Changed1 schema field changedv0.4.0Sep 3, 2026

addedInput schema / properties / include_snapshot

Added value: +{
+  "default": true,
+  "title": "Include Snapshot",
+  "type": "boolean"
+}

First observedv0.1.0Jun 20, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does so: it discloses automatic WAAP/PerimeterX Press & Hold handling, cookie-banner dismissal, error-on-failed-verification, and the subtle Akamai point that a clean 200 without a solved _abck is not clearance. These are exactly the non-obvious behaviors an agent could otherwise misjudge.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action and return shape lead, followed by challenge behavior, failure semantics, and the output-line grammar. Each sentence adds a distinct decision-relevant fact; the inline ``[index]<tag role=...>`` example earns its space by showing exact parseable format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still explains the snapshot line structure and the compact-summary alternative, which is the key formatting contract for chaining into click/type_text. For a three-parameter browser tool with no annotations, nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must supply meaning, and it does for both non-obvious flags: require_clearance is explained with the Akamai rationale and include_snapshot with its token-saving tradeoff and fallback. The required url parameter gets no elaboration, but it is self-evident, leaving only a minor gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (open a URL) plus the concrete artifact returned (indexed snapshot of interactive elements), and ties the index format to the sibling tools that consume it. Reading this alone, an agent can separate it from snapshot, fetch, or borrow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing rules: 'No separate challenge command is needed' steers away from detect_waap, and 'call snapshot() when you need the list' covers the include_snapshot=false case. It does not address when to prefer navigate over siblings like borrow or fetch (e.g. session reuse), so it stops short of full alternatives coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.