# Tyton (remote · mcp.usetyton.com)

Audit and set up Meta Pixel and the Conversions API from your AI agent.

- Trust score: 59/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `mcp.usetyton.com`: 59/100 (this document), [markdown](https://verifymcp.io/servers/com-usetyton-tyton/mcp.md), [page](https://verifymcp.io/servers/com-usetyton-tyton/mcp)

## Channel facts

- Endpoint: `https://mcp.usetyton.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (start_signup).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 5731 tokens (~212/item across 27 items; 27 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 57% of tool parameters carry a description.
  - Structured output schemas are declared (22% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Tyton MCP server?

Tyton is a hosted endpoint at https://mcp.usetyton.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-usetyton-tyton 'https://mcp.usetyton.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.com-usetyton-tyton]
url = "https://mcp.usetyton.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-usetyton-tyton": {
      "type": "remote",
      "url": "https://mcp.usetyton.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-usetyton-tyton --url 'https://mcp.usetyton.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-usetyton-tyton:
    url: "https://mcp.usetyton.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-usetyton-tyton": {
      "Transport": "http",
      "Url": "https://mcp.usetyton.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-usetyton-tyton -t streamable-http -u 'https://mcp.usetyton.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 56, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-18 (score 56)

First indexed and scored.

## MCP tools (27)

### `start_signup` (~179 tokens)

Create signup link

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, the customer's live https website. customer_approved records that the customer agreed to set up Tyton. Returns authorization_url for the customer, plus a private request_id and poll_token for checking the request's status. The customer can pick the free plan or a paid one; existing accounts with a plan skip that step. The link grants no access and starts no tracking by itself.

Input parameters:

- `audit_id` (string)
- `audit_key` (string)
- `client` (string)
- `customer_approved` (boolean, required)
- `site_url` (string): The customer's website (https) when there is no saved audit. The customer sees and approves it before connecting.

### `get_signup_status` (~89 tokens)

Check 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, this connection's server URL, private server key, public browser key and project. The suggested polling interval is 5 seconds. A connection is not tracking approval or activation.

Input parameters:

- `poll_token` (string, required)
- `request_id` (string, required)

### `delete_connected_project` (~137 tokens)

Delete connected site

Permanently deletes the Tyton project connected to this connection, including its keys, setup and stored event history. Requires confirmed: true and expected_url equal to the connected project's current URL; nothing is deleted if they differ. The account subscription and billing, the website itself and the Meta dataset and its data are unchanged. The Tyton snippet or SDK stays on the website until removed, and a browser Pixel already loaded there can keep sending to Meta until it is removed and the page reloads. A Meta request already in progress cannot be recalled. Requires a connected site.

Input parameters:

- `confirmed` (boolean, required)
- `expected_url` (string, required)

### `save_capi_token` (~186 tokens)

Save Conversions API 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_token (a sealed token from the Tyton browser extension, starting with `tyton_sealed_v1.`). The Pixel ID must match the site's saved Pixel. Meta checks the token; an explicit invalid or expired response is rejected, otherwise the token is saved with delivery unchecked. Saves the token encrypted; it is never returned. Does not send a test conversion, approve or activate tracking, or prove delivery. Requires a connected site with an active Tyton plan.

Input parameters:

- `capi_token` (string)
- `pixel_id` (string, required)
- `sealed_capi_token` (string): A sealed token from the Tyton browser extension, exactly as given (starts with tyton_sealed_v1.).

### `save_audit_to_project` (~73 tokens)

Link audit to site

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 linked report completes the checklist's audit step; it is not proof that tracking works. Requires a connected site.

Input parameters:

- `report_url` (string, required)

### `get_setup_progress` (~75 tokens)

Read setup progress

Reads the connected site's setup state in one compact response: plan approval, installation generation, missing callback sources, intentional pauses and the single next step. Read-only: makes no approval or activation and sends no test events. Callback evidence is not business success or Meta receipt. Verification-only setup works without Meta credentials. Requires a connected site.

### `check_live_setup` (~114 tokens)

Check live event receipts

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 installation ID and up to 20 unique event and source pairs. Read-only: sends no events and grants no approval. Verification callbacks are not live events. Reports receipt of the requested events only, not business outcomes, all site traffic, target or generation attribution, or Meta delivery. Requires a connected site.

Input parameters:

- `events` (array, required)
- `installation_id` (string, required)

### `get_sdk_installation` (~80 tokens)

Get SDK install instructions

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 the connection's server key; no npm publisher account or access to Tyton's repository is needed. Read-only: does not install, approve, start tracking or send events. Requires a connected site.

### `approve_conversion_plan` (~129 tokens)

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 confirmed: true and customer_confirmation with scope approve_plan. The connected key can approve only its own project; Tyton records connected-agent provenance, not verified human identity. Stale or changed revisions are rejected. Approval only: does not activate tracking or authorize live Meta events. The customer can also approve in the signed-in report.

Input parameters:

- `confirmed` (boolean, required)
- `customer_confirmation` (object, required)
- `digest` (string, required)
- `revision` (integer, required)

### `approve_and_start_conversion_plan` (~158 tokens)

Approve plan and request start

Records approval of an unchanged conversion plan proposal plus one start request, identified by revision, digest and request_id, after the customer explicitly accepted that scope in chat. The start runs only after the matching installation has fresh verified callbacks. Requires confirmed: true and customer_confirmation with scope approve_and_start_after_checks. A repeated request_id is treated as a retry of the same request. Requires a paired server key and the approval and execution features. Sends nothing now, bypasses no checks, and does not resume a paused, revoked, changed or restaged installation.

Input parameters:

- `confirmed` (boolean, required)
- `customer_confirmation` (object, required)
- `digest` (string, required)
- `request_id` (string, required)
- `revision` (integer, required)

### `read_conversion_installation` (~90 tokens)

Read installation state

Reads staged callback bindings, observed verification signals and the active or paused installation state for the connected site. Read-only. A verified callback proves receipt only, not business success or permission to send live. A matching pending approve-and-start request activates automatically after every fresh current-key check; otherwise the signed-in owner activates separately. Agents cannot activate manually. Active authorization does not prove live client deployment or Meta receipt.

### `stage_conversion_installation` (~185 tokens)

Stage installation

Stages callback bindings (conversion, target and a browser or server source) for the approved latest plan revision and digest under an installation generation. A matching generation is resumed; staging a new generation pauses the previous installation, clears verification and can cancel a pending start. Each enabled target needs a source, and Purchase requires a server source. Each binding reports through client.conversion(conversionId, targetId, data, {installationId: generation, eventId: stableOccurrenceId, verify: true}) on trusted confirmed success, not on a click, submit attempt or URL query parameter. Browser init with mode:'verify' suppresses automatic PageView and Pixel. A closed widget without a trustworthy success callback is unsupported. Does not activate tracking.

Input parameters:

- `bindings` (array, required)
- `digest` (string, required)
- `generation` (string, required)
- `revision` (integer, required)

### `read_conversion_plan` (~31 tokens)

Read conversion plan

Reads the connected site's current conversion plan draft, its open questions, approval state and review link. Read-only.

### `propose_conversion_plan` (~204 tokens)

Draft 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 is treated as a retry of the same change. Document: {schemaVersion:1,revision,conversions:[{id,label,enabled,eventName,targets:[{id,label,origin,path}],success:{kind,description}}]}. IDs are stable lowercase slugs; labels are distinct. Official Meta event names only. HTTPS origins only; a path has no query or fragment. Success kind: confirmed_success, checkout_started (InitiateCheckout only), or unresolved. 1 to 50 conversions, 1 to 20 targets each, 100 total, 32 KiB normalized document maximum. No tracking or verification fields. Returns the saved proposal, its open questions and the review link.

Input parameters:

- `document` (object, required)
- `expected_revision` (integer, required)
- `request_id` (string, required)

### `begin_audit` (~79 tokens)

Begin free 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 save, so a lost save response can be retried safely. Saves nothing. The capability covers only this audit record, not access to the website.

Input parameters:

- `url` (string, required)

Output parameters:

- `capturedAt` (string)
- `components` (array)
- `context` (array)
- `decision` (object)
- `findings` (array)
- `inventory` (object)
- `kind` (string)
- `limitations` (array)
- `nextActions` (array)
- `observations` (array)
- `reportSaved` (boolean)
- `reportUrl` (string)
- `schemaVersion` (string)
- `session` (object)
- `source` (string)
- `status` (string)
- `url` (string)

### `read_audit` (~129 tokens)

Read audit

Reads an existing audit using its private capability. Returns recorded context, scoped observations, provenance, component coverage, the current decision with open questions, and the report link. Read-only; does not verify the site's backend or grant access to it.

Input parameters:

- `audit_id` (string, required)
- `audit_key` (string, required)
- `request_id` (string): UUID identifying one mutation; a repeated request_id with identical content is treated as a retry
- `revision` (integer): latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write

Output parameters:

- `capturedAt` (string)
- `components` (array)
- `context` (array)
- `decision` (object)
- `findings` (array)
- `inventory` (object)
- `kind` (string)
- `limitations` (array)
- `nextActions` (array)
- `observations` (array)
- `reportSaved` (boolean)
- `reportUrl` (string)
- `schemaVersion` (string)
- `session` (object)
- `source` (string)
- `status` (string)
- `url` (string)

### `record_audit_context` (~209 tokens)

Record audit answers

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; availability_expectation records whether unavailable controls are expected. Both must have source human_reported. Earlier topics are kept; a new answer replaces the same topic. A public-only choice allows a partial report without further access requests. Returns the updated audit decision and report link.

Input parameters:

- `answers` (object, required)
- `audit_id` (string): audit run ID returned by Tyton; each audit run has its own ID
- `audit_key` (string): private audit write capability returned by Tyton; a secret that authorizes changes to this audit only
- `request_id` (string): UUID identifying one mutation; a repeated request_id with identical content is treated as a retry
- `revision` (integer): latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write
- `url` (string, required)

Output parameters:

- `capturedAt` (string)
- `components` (array)
- `context` (array)
- `decision` (object)
- `findings` (array)
- `inventory` (object)
- `kind` (string)
- `limitations` (array)
- `nextActions` (array)
- `observations` (array)
- `reportSaved` (boolean)
- `reportUrl` (string)
- `schemaVersion` (string)
- `session` (object)
- `source` (string)
- `status` (string)
- `url` (string)

### `record_audit_runtime` (~210 tokens)

Record runtime evidence

Saves bounded runtime evidence to the same audit run: sanitized observations from a real browser, authorized backend inspection or a destination UI, with the consent state and observation time. Does not run a browser or send events. A check whose evidence type does not prove it is stored as unknown. Returns the updated findings and report link.

Input parameters:

- `audit_id` (string): audit run ID returned by Tyton; each audit run has its own ID
- `audit_key` (string): private audit write capability returned by Tyton; a secret that authorizes changes to this audit only
- `checks` (array, required)
- `consent_state` (string, required)
- `observed_at` (string, required)
- `request_id` (string): UUID identifying one mutation; a repeated request_id with identical content is treated as a retry
- `revision` (integer): latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write
- `url` (string, required)

Output parameters:

- `capturedAt` (string)
- `components` (array)
- `context` (array)
- `decision` (object)
- `findings` (array)
- `inventory` (object)
- `kind` (string)
- `limitations` (array)
- `nextActions` (array)
- `observations` (array)
- `reportSaved` (boolean)
- `reportUrl` (string)
- `schemaVersion` (string)
- `session` (object)
- `source` (string)
- `status` (string)
- `url` (string)

### `connect` (~104 tokens)

Connect with pairing code

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 key and browser key, shown only once, with configuration examples for common MCP hosts.

Input parameters:

- `client` (string): which host is calling; used to label the new key
- `code` (string, required): the pairing code, e.g. 7K2M-QX4T (dashes optional)

### `audit_site` (~262 tokens)

Audit a public page

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 supplied by the agent, which is stored as unverified evidence. One session can hold several related components. Returns evidence, limitations and discovery actions, not a full tracking-health verdict.

Input parameters:

- `audit_id` (string): audit run ID returned by Tyton; each audit run has its own ID
- `audit_key` (string): private audit write capability returned by Tyton; a secret that authorizes changes to this audit only
- `fresh` (boolean): bypass the short public-page cache when verifying a change
- `html` (string): Authorized, sanitized page HTML, including local previews. The entire JSON-RPC request is limited to 256 KiB after JSON escaping, so a larger page needs a focused capture. Page markup only, without p…
- `request_id` (string): UUID identifying one mutation; a repeated request_id with identical content is treated as a retry
- `revision` (integer): latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write
- `url` (string, required): the site to audit

Output parameters:

- `capturedAt` (string)
- `components` (array)
- `context` (array)
- `decision` (object)
- `findings` (array)
- `inventory` (object)
- `kind` (string)
- `limitations` (array)
- `nextActions` (array)
- `observations` (array)
- `reportSaved` (boolean)
- `reportUrl` (string)
- `schemaVersion` (string)
- `session` (object)
- `source` (string)
- `status` (string)
- `url` (string)

### `setup_tracking` (~172 tokens)

Discover or configure site

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 connected project, it saves the project's site URL and Pixel ID; switching an existing Pixel or site requires confirm_change. Does not approve, install or activate tracking.

Input parameters:

- `checkout_domains` (array): hostnames where checkout happens, if already known
- `confirm_change` (boolean): true = yes, switch this project to a different Pixel ID or site URL on purpose
- `name` (string): project name; defaults to the site name
- `pixel_id` (string): Meta Pixel ID, numeric; optional while it is not yet known
- `url` (string, required): the site being tracked: a domain or full URL

### `setup_server` (~230 tokens)

Save server setup answers

Saves checkout and landing answers (payment provider, landing type and route, checkout domains) for the connected project and returns the reviewed server SDK success-callback contract. Does not install an integration or prove provider support; approval and activation are separate. Requires a connected site.

Input parameters:

- `backend` (string, required): where server code runs, as shown by the code (api, server or functions directories, or a separate service)
- `checkout_domains` (array): hostnames checkout lives on, if not the site itself ([] clears what's stored)
- `landing_marker` (string): what marks a purchase in the landing URL, e.g. ?checkout=success; often empty
- `landing_route` (string): e.g. /checkout/success or /dashboard; applies only to thank_you_page and app_route
- `landing_type` (string, required): where the person ends up after paying: a thank-you page, back in the app, nowhere (overlay checkout), or the provider's own screen
- `payment_provider` (string, required): who processes payments, as shown in code (package.json, env vars, webhook routes)

### `setup_status` (~52 tokens)

Read site configuration

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 approval, callback verification, activation or Meta receipt. Requires a connected site.

### `verify_install` (~84 tokens)

Check page HTML for Pixel

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 connected project. Read-only. Does not verify runtime callbacks, activation, consent behavior or Meta receipt. Requires a connected site.

Input parameters:

- `html` (string): page HTML fetched by the agent
- `url` (string, required)

### `tracking_status` (~59 tokens)

Read 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. Counts are not unique business conversions, current installation verification or proof of Meta deduplication. Requires a connected site.

### `submit_findings` (~587 tokens)

Submit code 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, backend location and existing Conversions API quality, plus the relative paths reviewed and any inapplicable checks with reasons. Unknown values stay unknown, not failed. Findings are stored as agent-reported, not verified deployed behavior. A group label is a label only; each report stays separate. Returns the updated audit decision and report link.

Input parameters:

- `audit_id` (string): audit run ID returned by Tyton; each audit run has its own ID
- `audit_key` (string): private audit write capability returned by Tyton; a secret that authorizes changes to this audit only
- `backend` (string): where the backend code is: in this repo, a separate repo not available here, or unknown
- `checkout_domains` (array): domains the checkout lives on, if separate; no customer paths or query strings
- `container_in_code` (string): Tyton container script embedded?
- `dedup_ids` (string): orderId/event_id on both browser and server events?
- `existing_capi` (object): grades for existing CAPI code, if any: hashes_pii (does it hash emails/phones before sending?), sends_event_id (does each server event include an event_id?), graph_version (which Graph API version, e…
- `framework` (string): frontend framework (from package.json deps)
- `group` (string): legacy grouping label only; does not combine reports or verify domain ownership
- `not_applicable` (array): Inapplicable checks, each with the actual reason, based on reviewed files and confirmed scope. Missing access counts as unknown, not N/A.
- `notes`: anything else found; a string or an array of strings
- `payment_provider` (string): payment processor used (from package.json, env vars, webhook routes)
- `pixel_in_code` (string): Meta Pixel initialized anywhere in the code?
- `request_id` (string): UUID identifying one mutation; a repeated request_id with identical content is treated as a retry
- `reviewed_files` (array): relative paths actually inspected in the relevant customer repository; no source code, absolute paths or secret files
- `revision` (integer): latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write
- `server_evidence` (string): one line: file/function where it was found
- `server_side_events` (string): code sends server-side events (CAPI/SDK/webhook)? unknown when not checked
- `url` (string, required): the site these findings belong to

Output parameters:

- `capturedAt` (string)
- `components` (array)
- `context` (array)
- `decision` (object)
- `findings` (array)
- `inventory` (object)
- `kind` (string)
- `limitations` (array)
- `nextActions` (array)
- `observations` (array)
- `reportSaved` (boolean)
- `reportUrl` (string)
- `schemaVersion` (string)
- `session` (object)
- `source` (string)
- `status` (string)
- `url` (string)

### `read_docs` (~133 tokens)

Read Tyton guidance

Returns Tyton guidance on one topic. meta_setup is the dashboard's nine-step Meta checklist (business, dataset, website, Conversions API token, testing), optionally a single step. website_management covers the website selector, per-project agent connections and deletion. Other topics: install, events, dedup, crawler_protection, create_pixel, create_business, consent, pricing, privacy, performance, gtm, platforms, faq. Read-only reference text, not saved checklist state or proof of delivery.

Input parameters:

- `step` (string): Optional Meta setup step; only used with topic meta_setup.
- `topic` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-usetyton-tyton/mcp#diagnostics

## Score history

- 2026-10-25: 59
- 2026-10-24: 59
- 2026-10-23: 58
- 2026-10-22: 58
- 2026-10-21: 57
- 2026-10-20: 57
- 2026-10-19: 56
- 2026-10-18: 56

## Common questions

### What is the Tyton MCP server?

Tyton is an MCP server listed in the public MCP registry as com.usetyton/tyton. Audit and set up Meta Pixel and the Conversions API from your AI agent. This page covers its hosted endpoint (https://mcp.usetyton.com/mcp).

### Is the Tyton MCP server safe to use?

Tyton scores 59 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Tyton MCP server expose?

Tyton exposes 27 tools: start_signup, get_signup_status, delete_connected_project, save_capi_token, save_audit_to_project, and 22 more. Their descriptions and schemas cost roughly 4,040 tokens of context every time the server is loaded.

### Does the Tyton MCP server require authentication?

No. We connected to Tyton without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Tyton MCP server still maintained?

Tyton is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.usetyton.com/mcp
- Repository: https://github.com/usetyton/tyton-mcp
- Website: https://usetyton.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-usetyton-tyton/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-usetyton-tyton/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-usetyton-tyton/mcp