FIDE Snap

com.fidenitPublished by fidenit.comOfficial publisherv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableFiles & StorageKnowledge & Memory

Overview

AI-generated overview

Lets an assistant search the screenshots and links a user saved in FIDE Snap, covering products, places, to-dos and articles.

What you can do
FIDE Snap is a remote MCP server, in beta, that connects an assistant to a personal collection of saved screenshots and links. The assistant can search that collection across categories such as products, places, to-dos and articles. No individual tools are documented in the supplied material, so the exact operations beyond search are not described.
When to use it
Worth adding when you keep screenshots and links in FIDE Snap and want an assistant to find things you saved earlier, for example a product, a place or an article, without browsing the collection yourself.
Requirements
A remote MCP endpoint at fidenit.com using streamable HTTP. Authentication is OAuth and required, so a FIDE Snap account is needed. No environment variables or headers are declared.
Before you install
The server reads a personal saved-items collection, so the assistant can see whatever you have stored there. Access is granted through OAuth; review which account you authorize and what scope the connection receives. The service is marked beta, so behavior and availability may change.

Installation

In SourceWeft

  1. Open FIDE Snap in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.fidenit%2Fsnap/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "fide-snap": {
      "type": "http",
      "url": "https://fidenit.com/api/snap/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 15, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.