This MCP server provides access to hosted public-page screenshots and PDFs. It uses a guarded Chromium environment to generate or render artifacts, and it exposes inline MCP artifacts as part of its workflow, according to the server description.

🛠️ Key Features

Hosted public-page screenshots
Hosted public-page PDFs
Guarded Chromium execution
Inline MCP artifacts

🚀 Use Cases

Retrieve screenshot outputs for public pages
Retrieve PDF outputs for public pages
Use MCP-generated artifacts in downstream automation

⚡ Developer Benefits

Integrates Model Context Protocol (MCP) with browser-rendered artifacts
Targets browser-automation use cases involving screenshots and PDFs
Includes topics coverage for mcp, pdf, screenshot, and browser-automation

⚠️ Limitations

Scope is limited to public-page screenshots and PDFs; no other artifact types are described.

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

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:

json

{
  "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.

Latchshot