Latchshot

io.github.BaiqingLPublished by GitHub account BaiqingLv1.0.2Updated Oct 24, 2026

Hosted public-page screenshots and PDFs with guarded Chromium and inline MCP artifacts.

VerifiedStreamable HTTPWeb executableBrowser Automation

Overview

AI-generated overview

Latchshot is a hosted service that lets an assistant capture screenshots and PDFs of public web pages through a remote MCP endpoint.

What you can do
Capture screenshots of public web pages using a guarded Chromium renderer hosted by the service. Produce PDF versions of public pages. Return the rendered output as inline MCP artifacts so results can be viewed directly in the conversation.
When to use it
Useful when you need a quick screenshot or PDF of a public page without running a browser locally, for example to show a page's current appearance or archive it as a document.
Requirements
A remote MCP connection to the hosted endpoint over streamable HTTP. A bearer API key is required in the Authorization header. The service advertises a free trial of recurring renders.
Before you install
The API key is a secret sent in the Authorization header; keep it private. Pages are rendered by a third-party hosted service, so the URLs you submit are sent to that provider. Only public pages are intended, and the service describes its Chromium as guarded.

Installation

In SourceWeft

  1. Open Latchshot in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.github.BaiqingL%2Flatchshot/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.

{
  "mcpServers": {
    "latchshot": {
      "type": "http",
      "url": "https://latchshot.fly.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

35% 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

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

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

  • License10 pts

    Declare a license in the repository or the registry entry.