mcpbeat

Screenshotink MCP Server

com.screenshotink/mcp
answering

Screenshotink is answering right now. Last checked 1 min ago. 52 installs a week from npm. Last commit 14 Jun 2026.

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

Installs per day peak 28 · avg 9 · +18% w/w
a month agotoday
Uptime history 39 hours of history · worst hour 67%
39 hours agonow
97.8%
Uptime 24h
90 of 92 checks
—
Tools
hidden behind auth
642 ms
Response time
average over 24h
52
Installs / week
npm and PyPI

Connect this server

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

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

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.screenshotink.com/mcp streamable-http needs key 634 ms 1 min ago

Screenshotink — questions

Answers built from our own checks of this server.

Why is there no tool list for Screenshotink?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 97.8% of checks in the last 24 hours got a reply.
Is Screenshotink working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 92 checks got a reply (97.8%), average response time 642 ms. The bar chart above shows every period we have measured.
How do I connect Screenshotink?
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. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Screenshotink need an API key?
Yes. Every time we knock, Screenshotink answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Screenshotink?
It answers our handshake in 642 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Screenshotink?
The npm package @screenshotink/mcp was installed 52 times in the last week. Week over week that is +18%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Screenshotink open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.