Tyton

Name: Tyton
Author: com.usetyton

MCP serverMCP

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

by com.usetytonrepository ↗homepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"tyton","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability27/27 checks ok

Endpoints

https://mcp.usetyton.com/mcpmcp streamable http · checked on a schedule

Registry facts

Not distributed through a package registry we index.

when	check	result	http	latency	detail
1 h ago	mcp initialize	ok	200	22 ms	server tyton 0.6.3 · protocol 2025-06-18 · 27 tools
9 h ago	mcp initialize	ok	200	72 ms	server tyton 0.6.3 · protocol 2025-06-18 · 27 tools
17 h ago	mcp initialize	ok	200	47 ms	server tyton 0.6.3 · protocol 2025-06-18 · 27 tools
24 h ago	mcp initialize	ok	200	22 ms	server tyton 0.6.3 · protocol 2025-06-18 · 27 tools
31 h ago	mcp initialize	ok	200	27 ms	server tyton 0.6.3 · protocol 2025-06-18 · 27 tools
2 d ago	mcp initialize	ok	200	73 ms	server tyton 0.6.3 · protocol 2025-06-18 · 27 tools
2 d ago	mcp initialize	ok	200	16 ms	server tyton 0.6.3 · protocol 2025-06-18 · 27 tools
2 d ago	mcp initialize	ok	200	9 ms	server tyton 0.6.3 · protocol 2025-06-18 · 27 tools
2 d ago	mcp initialize	ok	200	80 ms	server tyton 0.6.3 · protocol 2025-06-18 · 27 tools
3 d ago	mcp initialize	ok	200	90 ms	server tyton 0.6.3 · protocol 2025-06-18 · 27 tools

Tools observed via MCP handshake

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
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
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
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
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
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
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
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
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
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
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
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.
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 — 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
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
read_audit — Reads an existing audit using its private capability. Returns recorded context, scoped observations, provenance, component coverage, the current decision with o
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
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
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
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
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
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
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
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
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

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.usetyton/tyton

first seen 8 d ago · fetched 17 h agoopen ↗

Field history (7 recent events)

8 d ago · declared · summary → "Audit and set up Meta Pixel and the Conversions API from your AI agent."
8 d ago · declared · description → "Audit and set up Meta Pixel and the Conversions API from your AI agent."
8 d ago · declared · publisherName → "com.usetyton"
8 d ago · declared · homepageUrl → "https://usetyton.com"
8 d ago · declared · repoUrl → "https://github.com/usetyton/tyton-mcp"
8 d ago · declared · version → "1.0.0"
8 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from