# Usetyton Tyton MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.usetyton%2Ftyton
Registry id: `mcp-registry/com.usetyton/tyton`
Status: live (checked 2026-11-22T17:26:39.926Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 966
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "usetyton-tyton-mcp-server": {
      "type": "http",
      "url": "https://mcp.usetyton.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http usetyton-tyton-mcp-server https://mcp.usetyton.com/mcp
```

## Tools (27)

- `approve_and_start_conversion_plan`: Records approval of an unchanged conversion plan proposal plus one start request, identified by revision, digest and request_id, after the customer explicitly a
- `approve_conversion_plan`: Records approval of an unchanged conversion plan proposal, identified by its revision and digest, after the customer explicitly accepted it in chat. Requires co
- `audit_site`: Inspects one public page's HTML and saves a partial audit report, without signup. Takes the audit session fields and the page URL, plus optional sanitized HTML 
- `begin_audit`: Starts a new free audit session for a URL. Returns a private capability (audit_id and audit_key), revision 0 and an initial request_id for the first evidence sa
- `check_live_setup`: Checks whether specific PageView or conversion event IDs from an activated live installation reached Tyton's dashboard storage in the last 24 hours. Takes the i
- `connect`: Connects a Tyton site to this connection using a single-use pairing code from the site's card on usetyton.com (valid for 15 minutes). Returns the site's server 
- `delete_connected_project`: Permanently deletes the Tyton project connected to this connection, including its keys, setup and stored event history. Requires confirmed: true and expected_ur
- `get_sdk_installation`: Returns the private Tyton server SDK download, its SHA-256 checksum and the local-file install steps for the connected project. The download authenticates with 
- `get_setup_progress`: Reads the connected site's setup state in one compact response: plan approval, installation generation, missing callback sources, intentional pauses and the sin
- `get_signup_status`: Checks a signup and Connect request using its request_id and private poll_token. Returns waiting, unavailable or expired, or, after the site owner approves, thi
- `propose_conversion_plan`: Saves a conversion plan draft for the connected site. Does not approve or activate it. document.revision must equal expected_revision + 1; a repeated request_id
- `read_audit`: Reads an existing audit using its private capability. Returns recorded context, scoped observations, provenance, component coverage, the current decision with o
- `read_conversion_installation`: Reads staged callback bindings, observed verification signals and the active or paused installation state for the connected site. Read-only. A verified callback
- `read_conversion_plan`: Reads the connected site's current conversion plan draft, its open questions, approval state and review link. Read-only.
- `read_docs`: Returns Tyton guidance on one topic. meta_setup is the dashboard's nine-step Meta checklist (business, dataset, website, Conversions API token, testing), option
- `record_audit_context`: Saves answers about one audited component to the audit. audit_scope records the customer's choice between continuing the investigation and a public-only audit; 
- `record_audit_runtime`: Saves bounded runtime evidence to the same audit run: sanitized observations from a real browser, authorized backend inspection or a destination UI, with the co
- `save_audit_to_project`: Links an existing Tyton audit report to the connected website's Get Started checklist. Takes the report URL; only a report for this exact website is accepted. A
- `save_capi_token`: Saves a Meta Conversions API token for the connected site's current Pixel. Takes the Pixel ID plus exactly one of capi_token (the raw token) or sealed_capi_toke
- `setup_server`: Saves checkout and landing answers (payment provider, landing type and route, checkout domains) for the connected project and returns the reviewed server SDK su
- `setup_status`: Reads the connected project's configuration: site URL, Pixel ID, token status and saved checkout answers. Read-only. Configuration and token status are not plan
- `setup_tracking`: Discovers or configures reviewed v2 setup for a site. With only a URL it is read-only, needs no Pixel and returns setup guidance. With a real Pixel ID on a conn
- `stage_conversion_installation`: Stages callback bindings (conversion, target and a browser or server source) for the approved latest plan revision and digest under an installation generation. 
- `start_signup`: Creates a Tyton signup and Connect link for one website. Takes either a saved free audit (audit_id and audit_key, which brings the report along) or site_url, th
- `submit_findings`: Saves code review findings from the customer's repository to the audit: server-side events, dedup IDs, Pixel and container presence, payment provider, framework
- `tracking_status`: Reads aggregate browser and server event observations, delivery statuses, and the known-crawler protection mode and counts for the connected site. Read-only. Co
- `verify_install`: Checks a page's static HTML for Tyton container and Meta Pixel references, using a public fetch or HTML supplied by the agent, and compares them with the connec

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
