ascended-browser
Related Servers
Alternatives to ascended-browser
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to browse websites, extract information, fill forms, interact with pages, and execute multi-step web tasks autonomously.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search the web, read and extract content from webpages, fetch JSON from REST APIs, and collect links while bypassing anti-bot protections.35 npmISC
- AlicenseAqualityCmaintenanceEnables AI agents to fully control a browser for web automation, including navigation, clicking, typing, scrolling, screenshots, and DOM inspection, with session persistence and anti-bot bypass.4036 npmMIT

Outcrawl MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to read web pages as clean markdown or JSON, crawl sites, search the web with results already read, monitor pages for changes, and run multi-step browser tasks under configurable limits.MIT- AlicenseNot gradedqualityAmaintenanceEnables AI agents to navigate, interact with, search, extract from, and download from websites through anti-detection browser automation, with multi-tab workflows, session persistence, and batch operations.581 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control a real browser through intent-based tools—reading pages, filling forms, clicking, and replaying self-healing recipes—while returning only concise answers instead of the DOM.11 npm1MIT
TDQS
Scored across 11 tools
Tools cover distinct phases (navigate, observe, extract, act, screenshot, evaluate), and the descriptions explicitly cross-reference each other to route the agent (e.g. extract over evaluate for text, observe over screenshot for controls). The observe/extract/evaluate/screenshot cluster still has inherent overlap that only careful reading of the long descriptions resolves, so it is not perfectly self-evident.
Ten of eleven tools consistently use the browser_<verb>_<noun> snake_case pattern (browser_open, browser_extract, browser_act, browser_tabs). wait_for_bot_wall is the sole outlier with no prefix, though it is still readable and snake_case.
Eleven tools is well within the ideal range and each maps to a genuine browser-automation capability (navigation, login, observation, extraction, action, viewport, replay, screenshots, tab management, bot walls). No tool appears redundant or decorative.
The lifecycle is broadly covered: open, observe, extract, act, save/replay flows, screenshots, tabs, and viewport/auth emulation. Minor gaps remain around JS dialog handling, downloads, and cookie/storage inspection, which agents would occasionally need.