Use the private registry's manual path.
In Archestra, open MCP Registry, choose Add MCP Server to the Private Registry, then select Start from scratch. This path is built into the product and does not depend on the separate online catalog.
Archestra's public catalog reported 885 servers on July 19, 2026, but its API returned zero results for Latchshot. The official MCP Registry record is live; it is not yet an Archestra online-catalog entry.
Enter the remote contract exactly.
Use a personal scope for the first evaluation. A team or organization can broaden access later according to its Archestra policy.
| Archestra field | Value | Reason |
|---|---|---|
| Name | Latchshot | Short, recognizable private-registry label |
| Server Type | Remote | Archestra connects to the hosted service; it does not run Chromium |
| Server URL | https://latchshot.fly.dev/mcp | Stateless MCP Streamable HTTP endpoint |
| Authentication | Token header | Prompts for a secret during installation |
| Scope | Personal for the first test | Limits initial visibility while the tool is reviewed |
Selecting Token header currently seeds one header row. Before saving, verify that row rather than adding a second authorization header:
| Header property | Required value | What Archestra does |
|---|---|---|
| Header name | Authorization | Sends the credential on each MCP request |
| Scope | Installation | Asks the installing user instead of storing a shared plaintext default |
| Required header | On | Blocks installation until a token is supplied |
| Prepend “Bearer ” | On | Builds Authorization: Bearer <value> |
| Sensitive value | On | Treats the token as credential material |
The registry entry should describe how to request a credential. The actual ls_live_… value belongs in the installation prompt and must not enter exported configuration, issue text, screenshots, or source control.
Paste the token once, without its prefix.
After creating the entry, continue to Test Connection. When Archestra asks for the Authorization value, paste only the token beginning with ls_live_. Do not include the word Bearer; the header configuration adds it.
- Issue a recurring Free-plan key and save it when it is shown.
- Choose the smallest appropriate installation scope, normally Personal for evaluation.
- Paste the token into Archestra's masked installation field.
- Run the connection test, then continue only if tool discovery succeeds.
Authorization: Bearer <installation secret>A 401 at this step means the key is missing, malformed, or revoked. Repair the installation secret; changing the server URL or adding another header will not fix an invalid key.
Review two tools before assignment.
A successful connection should discover exactly capture_page and get_usage. Inspect the current definitions in Archestra's tool-review step before making either available to an agent.
| Tool | Effect | Guardrail decision |
|---|---|---|
get_usage | Reads plan, counters, quota remaining, reset time, and existing upgrade-request status | Read-only; it does not render a page or expose a payment action |
capture_page | Visits one public HTTP(S) target and returns an inline image or embedded PDF resource | Allow only where users or agents may send an external page visit and create an artifact |
Archestra exposes the raw tool definitions and per-tool guardrails in this step. Choose approval and assignment rules that match the agent's audience and data boundary; do not treat catalog or registry presence as a security decision.
Make the first request deliberately small.
Start with a public page that is stable and safe to revisit. A useful first instruction is:
Check Latchshot usage, then capture https://example.com
as a 1440 × 900 PNG. Do not retry if the target is rejected.The image should arrive inline with render time, navigation/font/script status, byte count, and remaining quota. For a PDF, request format: pdf and choose A4, Letter, or Legal paper. Use the broader MCP tool-contract guide for every bounded input.
Retry service faults, not policy rejections.
| Result | Meaning | Agent or operator action |
|---|---|---|
| Invalid target or option | The URL or capture settings violate the public-page contract | Fix the input; do not retry it unchanged |
| Unauthorized | The installation secret is missing, invalid, or revoked | Repair the credential and retest the connection |
| Rate or quota limit | The minute rate or monthly successful-render allowance is exhausted | Read the reset value and stop or defer the work |
| Queue unavailable | The bounded renderer is temporarily full | Retry at most twice with increasing delay |
| Render timeout | The target exceeded the server deadline | Retry once only when the page is known to be transient |
Only successful captures consume the monthly render allowance. A failed connection test or rejected target does not.
Keep private browsing inside your own network.
Latchshot is a hosted renderer for public pages. It rejects private, loopback, link-local, special-use, mixed public/private DNS, credential-bearing, and non-web-port destinations before and during navigation.
- No cookies, login sessions, arbitrary request headers, custom scripts, clicks, or form workflows.
- No CAPTCHA solving, residential proxies, anti-bot bypass, or private-network access.
- The target can observe a browser visit from Latchshot infrastructure.
- Archestra retains its registry, installation secret, tool assignments, and audit data according to the operator's deployment and policy.
Use a browser running inside the Archestra environment for authenticated or internal pages. Use Latchshot when the input is a public URL and the desired output is a bounded screenshot or PDF.
Separate compatibility from catalog acceptance.
This guide was checked against Archestra's public source and live catalog API on July 19, 2026, plus Latchshot's live MCP contract. Archestra's product source exposes the manual remote-server, token-header, connection-test, tool-review, and guardrail path described above.
Latchshot is published as io.github.BaiqingL/latchshot in the official MCP Registry. It is not currently an Archestra online-catalog listing, endorsement, install, user, or customer. Archestra is a third-party project and is not affiliated with Latchshot.
Start with 100 successful renders each month.
The Free plan renews every UTC calendar month and needs no card. Launch is $19 for 2,500 successful renders, Build is $49 for 12,000, and Scale is $149 for 50,000. Automatic overages are disabled.
Test one personal installation and one fixed public URL before sharing the registry item with a team or assigning capture_page to an autonomous agent.
Create the private registry entry.
Issue one Free key, configure the remote endpoint and installation-scoped token header, then inspect both tools before assigning them.