Snapy.host

host.snapyPublished by snapy.hostv1.1.2Updated Oct 25, 2026

Publish text or HTML to Snapy.host and get a shareable link that shows who opened it.

VerifiedSTDIODesktop only

Overview

AI-generated overview

Publishes text or HTML to Snapy.host and returns a shareable link that tracks who opened it.

What you can do
Publish text or HTML content to Snapy.host and get a shareable link. See who opened the published content through that link. Publishing and tracking run under the Snapy.host account tied to the API key.
When to use it
Use it when you want to turn text or HTML into a shareable link quickly and see who opened it. It is not suited to local-only previews or to content you do not want uploaded to a third-party service.
Requirements
Runs locally as the npm package snapy-mcp via npx over stdio, desktop only. Needs a free Snapy.host account with a verified email and the SNAPY_API_KEY environment variable set. Requires network access.
Before you install
Requires the SNAPY_API_KEY secret, so keep it private. Publishing uploads content to the third-party Snapy.host service, where it may be publicly shareable; avoid confidential or sensitive material. Published links can be opened by others.

Installation

In SourceWeft

  1. Open Snapy.host in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.2LatestSep 24, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.