In development

Your own endpoint. One pasted line.

Gateway already answers for any site with nothing installed. Install is for an owner who wants their own named endpoint and their own reviewed tool list — crawled, edited and saved by them, then registered with one script tag.

In development. The dashboard is real: sign in with a claimed domain, crawl it, toggle and edit what it proposes, and save. Every saved tool starts and stays unverified — this product has no per-action verification flow yet, the same gap Verifier names. The endpoint it produces, gateway.frontlatch.com/s/<your-domain>/mcp, is live and answers today, truthfully empty for every domain until that changes. The script tag itself has nothing to register against yet: the gateway does not answer its per-site script or discovery-file paths.

See your dashboardClaim your businessThe endpoint it is built on
A single brass socket lit warm in a dark wall-mounted patch panel, one cable plugged in among rows of unused sockets, a cold workshop out of focus behind it.

01Why it matters

A crawler can guess. An owner can be sure.

The Sydney index proposes actions from what a crawl finds. Install is the same crawl, handed to the owner first: review the name, the description and whether an agent should ask before it runs, before any of it is saved.

tools/list · a site-scoped endpoint, and the answer it gives today
POST https://gateway.frontlatch.com/s/example.com/mcp
{"jsonrpc": "2.0", "method": "tools/list", "id": 1}

{"jsonrpc": "2.0", "id": 1,
 "result": {"resultType": "complete", "tools": []}}

Live against gateway.frontlatch.com, confirmed 28 Sep 2026. Truthfully empty for every domain, saved or not, until the Action Graph store this compiles against exists — not a rate limit, not a permissions error, an honest empty list.

02How it works

  1. 01

    Crawl your site

    inspect_site proposes one tool per booking, quote, contact or callback form your claimed domain has.

  2. 02

    Toggle, edit, choose confirmation

    Include or leave out each one, rename it, rewrite its description, and decide whether it runs straight away or asks first.

  3. 03

    Save, then paste one line

    <script src="https://frontlatch.com/l.js" data-site="…"> registers whatever you saved, and writes the discovery link for you.

03In detail

The three outputs, from one saved schema

What one save produces, and how much of each is live today.
OutputAddressLive today?
The dashboard itself/app/my-site, below your claimed domainYes: crawl, toggle, edit, save, round-trip.
Hosted per-site endpointgateway.frontlatch.com/s/<your-domain>/mcpAnswers JSON-RPC. tools/list is empty for every domain until the Action Graph store lands.
WebMCP script + discovery file<script src=".../l.js" data-site="…"> and its .well-known filesNot yet: the gateway does not answer the per-site script or discovery paths the tag depends on.

All three are built from the identical saved schema, so they cannot drift from one another once wired — they are just not all wired yet.

04Evidence and limits

3

Outputs one saved install produces: a hosted endpoint, a WebMCP script and a discovery file.

0

Tools any per-site endpoint lists today, for any domain — truthfully empty, not a bug.

Confirmed live against the per-site endpoint this runThe endpoint it is built on

Claim your business first.

Install lives on your dashboard, under a claimed domain. Prove you control it, then crawl, toggle and save the tools you want it to propose.

Claim your businessSign in