web-api-extractor
Related Servers
Alternatives to web-api-extractor
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceA CDP-native MCP server that lets AI agents drive a real Chrome browser with deep network/console inspection, robust page interaction, and the ability to reverse-engineer a site's API flow into runnable code with dependency chaining and replay verification.5211 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with websites by capturing browser traffic and exposing them as named MCP tools, requiring no public API.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that connects to your browser to capture screenshots, inspect console logs, network requests, and more via Chrome DevTools Protocol.2 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to control Chrome/Edge browsers via CDP, including page navigation, element interaction, snapshots, network debugging, script execution, and performance tracing.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceExposes a live Chrome browser to any MCP client through a single local endpoint, enabling real-tab control, DOM interaction, cookies and session use, network/console capture, PDF export, and CDP-powered debugging.MIT
- AlicenseNot gradedqualityCmaintenanceCaptures browser network traffic, analyzes API patterns, and exposes analysis tools through an MCP server for AI-assisted workflows.1MIT
TDQS
Scored across 21 tools
Multiple tools overlap in purpose without descriptions, e.g., probe_login, http_login, open_browser_login all concern login but lack clarity; confirm_login, confirm_login_ready, and request_login_confirm_dialog have overlapping names and functions. Even described tools like confirm_login_ready and confirm_login could be confused for similar actions.
Most tools follow a verb_noun snake_case pattern (e.g., analyze_traffic, start_capture, list_sessions, export_project). A few exceptions like http_login and confirm_login_ready deviate slightly, but overall the naming convention is consistent and predictable.
21 tools is on the heavier side but not extreme. The server's scope (login, capture, diff, merge, generate) could justify this count, but many tools lack descriptions and some overlap, making the set feel bloated.
The server covers a full lifecycle from login and capture to diff, merge, and server generation. However, missing tools like list_endpoints or delete_endpoint create gaps, and 13 tools without descriptions make it hard to assess whether the surface is complete.