Feedthrough vs Periscope Mcp

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
Feedthrough
feedthrough
📂 Browser Automation
P
Periscope Mcp
segentic-lab
📂 Browser Automation
SummaryIn-browser debug bridge that injects into your running web app, so an agent can read the DOM, console logs and network requests, and click/fill/inspect the page. Runs inside the page (not an external CDP driver), so it works in any browser and inside Cypress/Playwright runs.Website & web-app testing built for AI agents rather than raw browser bindings: 66 Playwright tools with hard assertions, auto form-fill, persistent authenticated sessions (incl. interactive login for 2FA/SSO), network mocking, real INP, and accessibility/SEO/GEO (llms.txt, AI-crawler access, WebMCP) + Lighthouse audits.
Quality signal24/100 (Emerging)23/100 (Emerging)
Install pathnpx · highnpx · low
Engagement 0 0 0 4 0 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView FeedthroughView Periscope Mcp
More alternatives to FeedthroughMore alternatives to Periscope McpBrowser Automation category

Other servers like Feedthrough