MCP.Market

Snapshot Site MCP server

online · 100% uptime
by snapshot-site.com·com.snapshot-site/screenshots·v0.1.5·1 stars

Capture screenshots, detect visual regressions between page versions, and analyze with AI.

A95/100grade A
What users say
No reviews yet
Be the first
Safety scan
A95/100

full report

Adoption
Growing

1 stars28 downloads/wk

Reviews

Write one

Nobody has reviewed Snapshot Site yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Snapshot Site tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan11 source files scanned25/25
  • Live reliabilityremote reachable in 570ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 56 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10
Overall 95/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Snapshot Site compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
95/100
higher than 97% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
687 ms
faster than 20% of 30,031 servers
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
28
more than 15% of 12,191 servers with a package

Install Snapshot Site in Claude Code, Cursor or VS Code

claude mcp add --transport http screenshots https://mcp.snapshot-site.com/mcp
Add to Cursor

What the publisher says

From the Snapshot Site repository's README, as published. We do not edit it. Read it on GitHub

Snapshot Site MCP

Official MCP server for the Snapshot Site API

Tools

  • screenshot
  • analyze
  • compare

These tools are annotated for MCP clients as:

  • read-only
  • idempotent
  • open-world

They also include richer titles, category metadata, and example intents to improve tool selection in Claude Desktop and Cursor.

Two ways to connect

Hosted, with OAuth — point your client at https://mcp.snapshot-site.com/mcp and sign in. There is no local process to run and no API key in your client config; the server resolves your account from the OAuth session.

Local, with an API key — run the package yourself over stdio and provide SNAPSHOTSITEAPI_KEY. The server calls the Snapshot Site API directly.

Either way, calls count against the same plan quota as direct API calls. Nothing is metered differently because it came through MCP.

Credentials

The hosted server needs no credential — you sign in through OAuth and the server resolves your account from the session. Skip this section unless you run the server yourself over stdio.

For local stdio mode you need a Snapshot Site API key.

  1. Sign up for a Snapshot Site Console account.
  2. Create an API key on the API Keys page.

unless you're pointed at a self-hosted or staging instance.

  1. Pass the key to the server as the SNAPSHOTSITEAPI_KEY environment variable.
  2. Leave SNAPSHOTSITEBASE_URL at its default (https://api.prod.ss.snapshot-site.com)

Compatibility

Requires Node.js 20.9 or later. Built against @modelcontextprotocol/sdk v1.28 and tested with Claude Desktop and Cursor over stdio, and with any client that speaks the streamable HTTP transport against the hosted endpoint.

Usage

Not sure which options to use? Preview a capture and its parameters in the Screenshot console playground before wiring them into a tool call.

OAuth discovery flow

What a client does when connecting to the hosted server:

1. Discovery

Claude
  -> GET https://mcp.snapshot-site.com/.well-known/oauth-protected-resource

MCP
  -> responds:
     authorization_servers = https://mcp.snapshot-site.com
2. Authorization

Claude
  -> must know client_id
  -> opens:
     https://mcp.snapshot-site.com/oauth/v2/authorize
     ?client_id=...
     &redirect_uri=https://claude.ai/api/mcp/auth_callback
     &response_type=code
     &code_challenge=...
3. Token

Claude
  -> receives an access token
  -> calls the MCP server:
     POST https://mcp.snapshot-site.com/
     Authorization: Bearer <access_token>

The server then validates the token against the issuer and resolves the account it belongs to before running the tool.

Verifying the deployment

curl -s https://mcp.snapshot-site.com/.well-known/oauth-protected-resource | jq
curl -s https://mcp.snapshot-site.com/.well-known/openid-configuration | jq
curl -i https://mcp.snapshot-site.com/
curl -i -X POST https://mcp.snapshot-site.com/mcp -H 'content-type: application/json' --data '{}'

Manual vs implicit client_id

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Snapshot Site: common questions

Is Snapshot Site MCP server safe?
Yes, by our scan: it is graded A (95/100). Read the Snapshot Site safety report
How do I install Snapshot Site?
It runs remotely at mcp.snapshot-site.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Snapshot Site need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Snapshot Site maintained?
The last commit was 96 days ago (2026-07-30). The latest release is v0.1.5.
Is Snapshot Site up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Snapshot Site compare with other MCP servers?
safety score 95/100 (higher than 97% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 687 ms (faster than 20% of 30,031 servers). Full comparison.