mcpbeat Sign in

FIDE Snap MCP Server

answering

FIDE Snap is answering right now. Last checked 14 min ago.

Beta. Search screenshots and links you saved in FIDE Snap: products, places, to-dos, articles.

Uptime history 19 days of history
19 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
152 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check FIDE Snap every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 14 min ago.

run in your terminal
claude mcp add snap --transport http https://fidenit.com/api/snap/mcp
Settings → Connectors → Add custom connector, then paste this address
https://fidenit.com/api/snap/mcp
~/.codex/config.toml
[mcp_servers.snap]
url = "https://fidenit.com/api/snap/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "snap": {
      "url": "https://fidenit.com/api/snap/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "snap": {
      "type": "http",
      "url": "https://fidenit.com/api/snap/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://fidenit.com/api/snap/mcp streamable-http sign-in 126 ms 14 min ago

Alternatives to FIDE Snap

same job, measured the same way
ScreenVerb
by screenverb

Search, read and organize the screenshots in your ScreenVerb cloud library.

answering
Anylens
by slowper

Turn videos, PDFs, screenshots, and articles into anchored, cached understanding for agents.

63 installs/wk local only
JsonLink
by mauriblint

Web access for AI agents: URL to Markdown, link metadata, screenshots, links and images of any URL.

46 installs/wk local only
MagicScreenshots
by humanleap

Search real App Store screenshots and preview videos; generate and localize your own.

19 tools answering
ReMCP
by antonbaider

Securely use files, terminals, screenshots and processes on computers you pair with ReMCP.

answering
AppScreen
by stewones

Design App Store and Google Play screenshots in the AppScreen browser editor, live in your open tab.

answering
Document Scanner
by guardbee

Finds PII and credentials in PDFs, screenshots and scanned documents

954 installs/wk local only
UI Design to Code
by kinglions

Design-to-code artifact pipeline for UI screenshots, Figma node data, and visual review.

117 installs/wk local only

FIDE Snap — questions

Answers built from our own checks of this server.

Why is there no tool list for FIDE Snap?
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: 100.0% of checks in the last 24 hours got a reply.
Is FIDE Snap working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 152 ms. The bar chart above shows every period we have measured.
How do I connect FIDE Snap?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to FIDE Snap?
No API key is involved. FIDE Snap answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is FIDE Snap?
It answers our handshake in 152 ms on average, which is faster than 80% 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.