A
licenseNot graded
qualityC
maintenanceEnables agents to take screenshots and extract text from web pages using a persistent Chrome browser via CDP, with built-in SSRF protection.
191 npm
MIT
fullpageshot-mcp
Related Servers
Alternatives to fullpageshot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to capture screenshots, scrape structured page content, and run automated visual checks on live websites via a headless Chromium browser.3MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to capture web pages or render HTML as images or PDFs, with screenshots returned inline to the assistant.351 npmMIT
Grabbitofficial
AlicenseNot gradedqualityCmaintenanceScreenshot MCP for agents. Send a public URL, get a pixel-perfect CDN image. Full page, header, mobile, or custom. Cookie banner suppression. Handles sites that block headless browsers. Works with Claude, Cursor, Codex. $0.002/grab.MIT- AlicenseAqualityDmaintenanceEnables AI assistants to capture screenshots of web pages using automated browser sessions. Supports full-page and element-specific screenshots, device simulation, and JavaScript execution for comprehensive web testing and monitoring.618 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to open public http(s) URLs in headless Chromium and receive back PNG screenshots, accessibility snapshots, and visible page text in a single tool call, with SSRF protections blocking private and local addresses.MIT
TDQS
A3.6/5.0
Scored across 5 tools
Disambiguation4/5
Each tool targets a distinct action on the controlled browser: open, capture, read file, close, and report status. The only mild overlap is that screenshot can accept a URL directly, which slightly blurs the line with open_url, but otherwise the boundaries are clear.
Naming Consistency4/5
Most tools follow a verb_noun pattern (open_url, read_screenshot, close_browser) which is consistent and readable. screenshot and browser_status deviate (noun-only), but the set is still predictable.
Tool Count4/5
Five tools is a snug, well-scoped set for a headless-browser screenshot server, covering the core lifecycle without bloat. It sits at the lower end but each tool earns its place.
Completeness4/5
The browser lifecycle is well covered: open, capture, read back, close, and status. Minor gaps like page interaction (click, scroll, navigate) exist, but for a screenshot-focused purpose the surface is essentially complete.