Wraith MCP Server
Related Servers
Alternatives to Wraith MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides a real browser that bypasses bot detection (Cloudflare, Turnstile) for AI agents, enabling navigation, clicking, typing, screenshots, and data collection through MCP tools.44MIT
- AlicenseNot gradedqualityCmaintenanceProvides a headless Chromium browser through MCP, enabling AI agents to browse JavaScript-rendered pages, search the web, capture screenshots, extract tables and data, and run stateful multi-step interactions like clicking, typing, and form submission.780,5681MIT
- AlicenseBqualityAmaintenanceProvides AI agents with a real browser environment for web automation, memory, and secure credential management through 15 MCP tools.15MIT
- AlicenseAqualityBmaintenanceEnables AI agents to control a browser via MCP with structured perception, verified actions, and self-healing capabilities.13161MIT
- AlicenseCqualityCmaintenanceProvides browser automation and web scraping as MCP tools, enabling autonomous URL ingestion, crawling, extraction, and anti-bot handling with interactive browser control.625MIT
- AlicenseAqualityBmaintenanceA lightweight, stealthy headless browser for AI agents, providing MCP tools for web extraction, interaction, and snapshotting.121Apache 2.0
TDQS
Scored across 15 tools
Most tools target clearly distinct actions: navigate/click/type/scroll/read/screenshot all have separate roles. The main ambiguity is among the identity-injection tools (borrow, ensure_high_score, receive_profile), which all involve injecting cookies and could be confused despite detailed descriptions.
All names are lowercase snake_case and mostly verb-led, but the pattern is mixed: some are bare verbs (navigate, click, scroll, fetch), some are verb_noun (type_text, fill_secret, save_state), and browser_tabs breaks the verb convention entirely. It is readable but not a uniform pattern.
At 15 tools, the set is at the upper edge of the typical well-scoped range, but each tool addresses a distinct part of the anti-bot browsing workflow—detection, navigation, interaction, identity borrowing, session persistence, and no-browser fetching. The count feels justified for the complexity of the domain.
The surface covers the full core lifecycle: detect defenses, navigate, interact, authenticate, persist sessions, and extract content. Minor gaps exist—there is no explicit wait-for-element, back/reload, or general DOM query tool—but agents can work around these with snapshot/click/scroll.