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.50 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.4024 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.29 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with web browsers using natural language, featuring automated browsing, form filling, vision-based element detection, and structured JSON responses for systematic browser control.62MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a browser through a set of tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.-
TDQS
A4.4/5.0
Scored across 10 tools
Disambiguation4/5
Most tools target clearly different browser operations, but the read-side tools (browser_observe, browser_extract, browser_evaluate, browser_screenshot) overlap in purpose and require the long descriptions to separate them. The descriptions do provide strong guidance, so an agent can usually pick correctly, but some ambiguity remains.
Naming Consistency4/5
Nine tools use a consistent snake_case browser_ prefix, and the naming is readable and predictable. The lone exception is wait_for_bot_wall, and some browser_ tools are noun-based rather than verb-based, which are minor deviations.
Tool Count5/5
Ten tools is well-scoped for a browser automation server, with each tool covering a distinct capability such as opening, acting, observing, extracting, screenshotting, viewport control, flow replay, and bot-wall handling. No tool feels redundant or missing at the count level.
Completeness5/5
The surface covers the browser lifecycle: opening/navigating, tab management, interaction, observation, extraction, evaluation, screenshots, viewport emulation, workflow replay, and bot-wall handling. There are no obvious dead ends for typical browser automation tasks.
Maintenance
ActivityNo data
ResponsivenessNo issues