F
licenseNot graded
qualityB
maintenanceEnables AI assistants to browse websites, extract information, fill forms, interact with pages, and execute multi-step web tasks autonomously.
-
ascended-browser
by AceAtDev
Related Servers
Alternatives to ascended-browser
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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.19 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.4012 npmMIT
- 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.201 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.01MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control a real, authenticated Chrome browser through native tools for navigation, DOM interaction, form filling, scraping, screenshots, and human-in-the-loop checkpoints while minimizing tokens and latency.MIT
TDQS
A4.3/5.0
Scored across 11 tools
Disambiguation4/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues