A
licenseA
qualityC
maintenanceMCP server + Chrome extension that gives AI coding agents control of your real browser with existing sessions, logins, and cookies. Works with Cursor, Claude, Windsurf.
18
354 npm
55
MIT
intruder-mcp
Officialby intruder-io
Related Servers
Alternatives to intruder-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables browser automation through MCP clients like Claude or Cursor, using the client's existing LLM without requiring an additional API key.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables programmatic control of Cursor's cloud-based AI agents for automated code generation and repository management via standardized MCP tools.16 npm6MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server wrapping the Cursor CLI agent, enabling Claude Code and other MCP clients to delegate tasks to Cursor's AI agent for file writing, bash commands, and codebase queries.-
- AlicenseAqualityAmaintenanceEnables MCP clients such as Claude and Cursor to control an isolated cloud machine with a real browser, shell, filesystem, and web access, so agents can navigate pages, click and type, run commands, manage files, and search or fetch web content.26577 npm1MIT
- AlicenseAqualityCmaintenanceEnables Claude and Cursor to access agent memory, shared knowledge graphs, and decision audit through MCP.12MIT
TDQS
A3.5/5.0
Scored across 21 tools
Disambiguation4/5
Tools map cleanly to distinct resources and actions (scans, schedules, targets, tags, issues, occurrences), so misselection is unlikely. Minor overlap exists between get_scan/list_scans and list_occurrences/get_scanner_output, but the single-vs-list and output-vs-metadata distinctions are clear enough.
Naming Consistency5/5
Every tool follows a strict verb_noun pattern (get_status, create_scan, list_targets, delete_scan_schedule, etc.) with no style mixing. The only trivial wrinkle is plural 'create_targets' vs singular tag tools, which does not impede predictability.
Tool Count4/5
21 tools is on the heavier side but justified by a genuinely broad domain spanning scans, schedules, targets, tags, issues, occurrences, licenses, and user context. Each tool corresponds to a distinct operation, though a few (get_status, get_user) are minor conveniences.
Completeness4/5
Core lifecycle coverage is strong: schedules have full CRUD, scans support create/list/get/cancel, and targets/issues/occurrences support the main workflow operations. Gaps like no single get_target, no get_issue detail, and no update_target are minor and workable around.
Maintenance
ActivityMaintained
ResponsivenessResponsive