Ritoko
Related Servers
Alternatives to Ritoko
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables any agent to drive a dedicated Chromium instance through MCP, including opening and reading pages, taking steps, logging in via a password vault, downloading/uploading files, and replaying saved routines. It also gates sensitive actions behind approvals and can use client certificates or one-time card data for official procedures.MIT
- AlicenseNot gradedqualityDmaintenanceEnables creation of reusable browser automation skills through demonstration by recording user actions in a browser while narrating, then converting those workflows into executable skills that can be invoked through natural language.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables governed browser automation for AI agents with human-in-the-loop approval, audit logging, and read-only replay, supporting both ASK and AUTO autonomy modes.MIT
- AlicenseBqualityDmaintenanceEnables AI-driven browser automation with advanced form testing, batch operations, and intelligent element extraction for MCP-compatible applications.1413 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to scan web UI screens, follow login and test-case flows, and generate verified XPath locator .properties files with one unique locator per element, including support for iframes, SSO/MFA, proxies, and internal networks.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to batch repetitive web admin work by harvesting queue items read-only, collecting verdicts, and applying them only after human approval, with dry runs, staged rollout, rate limits, a circuit breaker and an audit log. Also provides general browser control — navigating, reading, filling forms and clicking on allowed sites through an already logged-in local browser, pausing for confirmation before irreversible actions.MIT
TDQS
Scored across 20 tools
Tools are well-differentiated by clear verb_noun naming (browser_open vs browser_snapshot, run_start vs run_resume vs run_cancel, host_start vs host_next). Minor overlap exists between run_resolve and run_reconcile (both handle review items) and between run_cancel and run_resume (both alter run state), but descriptions explain the boundaries well. An agent can reliably pick the right tool.
Consistent snake_case with predictable domain prefixes: browser_*, run_*, workflow_*, host_*, plus single verbs document_image, recording, doctor, step_repair. The pattern is readable and groups tools by lifecycle area.
20 tools is on the heavier side but justified by a genuinely broad domain: browser automation, workflow authoring, direct runs, host runs, and diagnostics. Each tool maps to a distinct lifecycle stage; nothing feels redundant, though the surface is near the upper bound of comfortable scoping.
Full lifecycle coverage across every sub-domain: recording (browser_open, browser_act, recording), authoring (workflow_save/get/list), execution (run_start, run_resume, run_cancel, host_start, host_next), recovery (step_repair, run_reconcile, run_resolve, run_adopt), inspection (run_report, run_list, doctor, document_image). No obvious dead ends for the stated purpose.