Latchshot MCP server

Latchshot gives MCP clients guarded screenshots and PDFs of public web pages through hosted Chromium. It uses a remote Streamable HTTP endpoint, so clients do not need a local browser or package installation.

Endpoint: https://latchshot.fly.dev/mcp
Transport: stateless MCP Streamable HTTP with JSON responses
Authentication: Authorization: Bearer ls_live_...
Free plan: 100 successful renders per UTC calendar month, no card
Documentation: https://latchshot.fly.dev/docs.md#hosted-mcp-server
Get a key: https://latchshot.fly.dev/?intent=mcpmetadata#trial
Official MCP Registry: io.github.BaiqingL/latchshot
Glama connector: io.github.BaiqingL/latchshot
Source metadata: https://github.com/BaiqingL/latchshot-mcp

First successful capture

Create a recurring Free-plan key. It includes 100 successful renders per UTC calendar month and requires no card.
Add the fixed remote endpoint to your MCP client using one of the configurations below. Keep the key in the client's secret or credential manager.
Ask the client:

Capture https://example.com as a 1200×630 JPEG.

A successful call returns the image inline with render diagnostics and remaining quota. A failed render returns a bounded error and does not consume quota. Then ask Check my Latchshot usage to call the read-only get_usage tool; its optional plan links initiate neither payment nor an upgrade.

Registry and security review

The official Registry record reports 1.0.2 active/latest and links this verified repository (id: 1305296171).
Tagged metadata releases are schema-validated and published through GitHub Actions with OIDC; the workflow stores no Registry credential.
The remote endpoint requires Bearer authentication. An unauthenticated MCP initialization request returns HTTP 401, WWW-Authenticate: Bearer, and a bounded JSON-RPC error without exposing tools or credentials.
The public /healthz check reports service and render-queue availability without requiring a key or exposing customer data.
Security reports use this repository's private vulnerability reporting. Do not put keys, private URLs, customer data, or exploit details in a public issue.

These checks establish the published contract and review path. They do not claim a third-party catalog listing, install, user, customer, conversion, endorsement, or service-level agreement.

Tools

`capture_page`

Captures a public HTTP(S) URL as PNG, JPEG, or PDF. Images are returned as inline MCP image content and PDFs as embedded MCP resources. The result also includes render time, navigation/font/script status, and remaining quota when applicable.

The tool supports bounded viewport size, full-page images, dark mode, an extra readiness delay, and PDF paper/orientation. Private, loopback, link-local, mixed public/private DNS, special-use, and metadata-network targets are blocked.

`get_usage`

Returns the current plan, successful-render usage, remaining quota, reset time, and any existing upgrade-request status for the API key.

The MCP server intentionally exposes no payment or upgrade tool.

Client configuration

Store the API key in the client's secret or credential manager. A representative remote-server configuration is:

VS Code

Create a recurring Free-plan key, then add Latchshot to VS Code with its supported CLI path:

code --add-mcp '{"name":"latchshot","type":"http","url":"https://latchshot.fly.dev/mcp","headers":{"Authorization":"Bearer ${input:latchshot-api-key}"},"inputs":[{"type":"promptString","id":"latchshot-api-key","description":"Latchshot API key","password":true}]}'

VS Code prompts for the key on first start and masks the input. The fixed endpoint and placeholder are safe to keep in configuration; do not replace the placeholder with a real key in a shared file. See the complete five-client install guide for VS Code, Cursor, Claude Code, Gemini CLI, and goose.

Generic remote configuration

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

Configuration keys and environment-variable interpolation differ between clients. Do not commit a real key to a repository.

Scope and safety

Latchshot is for public pages that the customer has the right to capture. It does not offer cookies, authenticated sessions, arbitrary browser scripts, CAPTCHA solving, proxy rotation, private-network rendering, or anti-bot bypass. Only successful captures consume quota.

Repository scope

This repository publishes the remote server's MCP Registry metadata and public integration documentation. It does not contain the hosted renderer, customer store, infrastructure configuration, or credentials. The metadata and documentation in this repository are MIT licensed; use of the hosted service is governed by its published service terms.

Versioning

The MCP Registry version tracks the public tool contract and discovery metadata. v1.0.1 added the verified GitHub repository identity used by downstream registries. v1.0.2 adds an attributable recurring-Free-plan continuation to the Registry credential description; neither version changes tools or transport. Breaking tool changes will receive a new major version.