mcpbeat Sign in

ScreenshotMCP MCP Server

by agentforge-labs Your server? Claim it
not responding

ScreenshotMCP is listed as active in the registry but did not answer our last check. It exposes 2 tools.

Desktop and mobile website screenshots plus page context for AI agents and automation workflows.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 47 days of history · worst day 95%
47 days agonow
98.9%
Uptime 24h
91 of 92 checks
2
Tools
read from the server
133 ms
Response time
average over 24h
open, no key
Access
streamable-http

ScreenshotMCP missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add site-screenshot --transport http https://snapforge.web-tasarimci.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "site-screenshot": {
      "url": "https://snapforge.web-tasarimci.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.site-screenshot]
url = "https://snapforge.web-tasarimci.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "site-screenshot": {
      "url": "https://snapforge.web-tasarimci.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "site-screenshot": {
      "url": "https://snapforge.web-tasarimci.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

capture
capture_website
Capture desktop, mobile, or both screenshots for a website. Successful screenshots are reused from cache until TTL expiry; failed or blocked captures are never cached and are retried live on the next call.
page
read_page_context
Render a public web page and return a compact Community agent-readable representation: visible text, clean Markdown, headings, links, forms, basic image metadata and interactive elements with bounding boxes. No OCR, visual inference, crawl, sessions or advanced action selectors.

Endpoints

URLTransportStateLatencyChecked
https://snapforge.web-tasarimci.com/mcp streamable-http answering 8060 ms 6 min ago

Alternatives to ScreenshotMCP

same job, measured the same way
Anode background Windows desktop
by skulitom

Background Windows desktop for AI agents: native GUI automation, screenshots and app testing.

local only
Screenshotink
by screenshotink

Screenshot, diff, audit and sitemap-capture any web page — 5 MCP tools for AI agents.

26 installs/wk answering
Android Puppeteer MCP
by pedro-rivas

MCP server for Android automation with UI interaction, screenshots, and device control

90 installs/wk local only
Figma Context MCP Air
by compassalessandrolorenz

Figma MCP server for AI agents. 9 tools: design context, variables, screenshots, and FigJam.

24 installs/wk local only
Capturewren: Website Screenshot API for AI Agents (Image + Text)
by shawmena-dotcom

Capturewren: screenshot any URL (banners removed) plus status, title and clean page text for agents.

answering
Capturewren: Website Screenshot API for AI Agents (Image + Text)
by cybermax-tools

Capturewren: screenshot any URL (banners removed) plus status, title and clean page text for agents.

answering
Capturewren: Website Screenshot API for AI Agents (Image + Text)
by workers-cybermax-tools-cybermax

Capturewren: screenshot any URL (banners removed) plus status, title and clean page text for agents.

answering
RokuMCP
by jack1590

MCP server for Roku device automation — deploy, ECP control, screenshots, and debug console

456 installs/wk local only

ScreenshotMCP — questions

Answers built from our own checks of this server.

What can ScreenshotMCP do?
It exposes 2 tools, read directly from the server on our last check. Among them: capture_website, read_page_context. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is ScreenshotMCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 133 ms. The bar chart above shows every period we have measured.
Is ScreenshotMCP still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists ScreenshotMCP as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect ScreenshotMCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does ScreenshotMCP need an API key?
No. ScreenshotMCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is ScreenshotMCP?
It answers our handshake in 133 ms on average, which is faster than 78% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.