Wraith MCP Server

Overview Schema Source Related Servers Discussions Admin

fetch

Replay a captured authenticated session against a URL with a real-browser TLS fingerprint and no browser launch, returning status, classification, and body preview.

Instructions

No-browser TLS-impersonation request — the cheap fast path.

Replays a captured session against url with a real-browser TLS+HTTP2 fingerprint and NO browser launch. session_file is a JSON file with {headers:{Authorization,Cookie,User-Agent}} (as written by wraith harvest / the borrow flow). Use this to replay an already-authenticated/cleared session cheaply; escalate to navigate only when the returned classification is challenge. Returns the status, classification, and a body preview.

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": "fetch"
  }
}

Input Schema

Name	Required	Default
`url`	Yes
`method`	No	GET
`impersonate`	No
`session_file`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0Sep 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations present, the description carries the full burden and mostly succeeds: it discloses no-browser execution, TLS fingerprinting, session replay semantics, and the returned status/classification/body preview. It does not mention error behavior for a missing session_file, but the core behavioral traits are clear.

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?

Three sentences, front-loaded with the most important distinction and no filler. Every sentence contributes either usage guidance, the session-file format, or the routing rule.

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?

The description covers the tool's niche, how to obtain a session file, what to do on challenge classification, and what the response contains. Given the output schema exists, return-value detail is appropriately minimal.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It does explain url and session_file, including the JSON shape, but method and impersonate are left undocumented beyond their names and defaults. This leaves a clear gap for two optional parameters.

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?

The description opens with a specific verb and resource: 'No-browser TLS-impersonation request' targeting a URL. It clearly distinguishes this tool from siblings like navigate by emphasizing 'NO browser launch' and 'cheap fast path'.

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

Usage Guidelines5/5

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

Explicit guidance is provided: 'Use this to replay an already-authenticated/cleared session cheaply; escalate to navigate only when the returned classification is challenge.' This tells the agent exactly when to use this tool and when to switch to an alternative.

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