com.usetyton/tyton

Est-ce que com.usetyton/tyton est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.usetyton/tyton » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 27 outils

• approve_and_start_conversion_plan≈ 427 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • digest · string · requis
  • revision · integer · requis
  • confirmed · boolean · requis · True
  • request_id · string · requis
  • customer_confirmation · object · requis

  Exemple d'appel

  {"name": "approve_and_start_conversion_plan", "arguments": {"digest": "texte", "revision": 1, "confirmed": true, "request_id": "texte", "customer_confirmation": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• approve_conversion_plan≈ 377 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • digest · string · requis
  • revision · integer · requis
  • confirmed · boolean · requis · True
  • customer_confirmation · object · requis

  Exemple d'appel

  {"name": "approve_conversion_plan", "arguments": {"digest": "texte", "revision": 1, "confirmed": true, "customer_confirmation": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• audit_site≈ 1810 tokens

  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.

  Paramètres, retour & exemple (7)

  Paramètres

  • url · string · requis
    the site to audit
  • html · string · optionnel
    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 private source or personal data.
  • fresh · boolean · optionnel
    bypass the short public-page cache when verifying a change
  • audit_id · string · optionnel
    audit run ID returned by Tyton; each audit run has its own ID
  • revision · integer · optionnel
    latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write
  • audit_key · string · optionnel
    private audit write capability returned by Tyton; a secret that authorizes changes to this audit only
  • request_id · string · optionnel
    UUID identifying one mutation; a repeated request_id with identical content is treated as a retry

  Exemple d'appel

  {"name": "audit_site", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "kind": "session", "source": "live_fetch", "status": "partial", "context": [], "session": {}, "decision": {}, "findings": [], "inventory": {}, "reportUrl": "texte", "capturedAt": "texte", "components": []}}

• begin_audit≈ 1514 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis

  Exemple d'appel

  {"name": "begin_audit", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "kind": "session", "source": "live_fetch", "status": "partial", "context": [], "session": {}, "decision": {}, "findings": [], "inventory": {}, "reportUrl": "texte", "capturedAt": "texte", "components": []}}

• check_live_setup≈ 373 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • events · array · requis
  • installation_id · string · requis

  Exemple d'appel

  {"name": "check_live_setup", "arguments": {"events": [], "installation_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• connect≈ 205 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • code · string · requis
    the pairing code, e.g. 7K2M-QX4T (dashes optional)
  • client · string · optionnel · cursor | claude_code | other
    which host is calling; used to label the new key

  Exemple d'appel

  {"name": "connect", "arguments": {"code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_connected_project≈ 270 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • confirmed · boolean · requis · True
  • expected_url · string · requis

  Exemple d'appel

  {"name": "delete_connected_project", "arguments": {"confirmed": true, "expected_url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_sdk_installation≈ 170 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_sdk_installation", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_setup_progress≈ 174 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_setup_progress", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_signup_status≈ 192 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • poll_token · string · requis
  • request_id · string · requis

  Exemple d'appel

  {"name": "get_signup_status", "arguments": {"poll_token": "texte", "request_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• propose_conversion_plan≈ 722 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • document · object · requis
  • request_id · string · requis
  • expected_revision · integer · requis

  Exemple d'appel

  {"name": "propose_conversion_plan", "arguments": {"document": {}, "request_id": "texte", "expected_revision": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• read_audit≈ 1615 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • audit_id · string · requis
  • revision · integer · optionnel
    latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write
  • audit_key · string · requis
  • request_id · string · optionnel
    UUID identifying one mutation; a repeated request_id with identical content is treated as a retry

  Exemple d'appel

  {"name": "read_audit", "arguments": {"audit_id": "texte", "audit_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "kind": "session", "source": "live_fetch", "status": "partial", "context": [], "session": {}, "decision": {}, "findings": [], "inventory": {}, "reportUrl": "texte", "capturedAt": "texte", "components": []}}

• read_conversion_installation≈ 206 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "read_conversion_installation", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• read_conversion_plan≈ 108 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "read_conversion_plan", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• read_docs≈ 311 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • step · string · optionnel · business | pixel | domain | token | installed | browser_seen | server_seen | dedup
    Optional Meta setup step; only used with topic meta_setup.
  • topic · string · requis · meta_setup | website_management | install | events | dedup | crawler_protection | create_pixel | create_business

  Exemple d'appel

  {"name": "read_docs", "arguments": {"topic": "meta_setup"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• record_audit_context≈ 2479 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

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

  Exemple d'appel

  {"name": "record_audit_context", "arguments": {"url": "texte", "answers": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "kind": "session", "source": "live_fetch", "status": "partial", "context": [], "session": {}, "decision": {}, "findings": [], "inventory": {}, "reportUrl": "texte", "capturedAt": "texte", "components": []}}

• record_audit_runtime≈ 1937 tokens

  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.

  Paramètres, retour & exemple (8)

  Paramètres

  • url · string · requis
  • checks · array · requis
  • audit_id · string · optionnel
    audit run ID returned by Tyton; each audit run has its own ID
  • revision · integer · optionnel
    latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write
  • audit_key · string · optionnel
    private audit write capability returned by Tyton; a secret that authorizes changes to this audit only
  • request_id · string · optionnel
    UUID identifying one mutation; a repeated request_id with identical content is treated as a retry
  • observed_at · string · requis
  • consent_state · string · requis · unknown | not_interacted | accepted | declined | no_banner_observed

  Exemple d'appel

  {"name": "record_audit_runtime", "arguments": {"url": "texte", "checks": [], "observed_at": "texte", "consent_state": "unknown"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "kind": "session", "source": "live_fetch", "status": "partial", "context": [], "session": {}, "decision": {}, "findings": [], "inventory": {}, "reportUrl": "texte", "capturedAt": "texte", "components": []}}

• save_audit_to_project≈ 180 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • report_url · string · requis

  Exemple d'appel

  {"name": "save_audit_to_project", "arguments": {"report_url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• save_capi_token≈ 322 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • pixel_id · string · requis
  • capi_token · string · optionnel
  • sealed_capi_token · string · optionnel
    A sealed token from the Tyton browser extension, exactly as given (starts with tyton_sealed_v1.).

  Exemple d'appel

  {"name": "save_capi_token", "arguments": {"pixel_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• setup_server≈ 464 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

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

  Exemple d'appel

  {"name": "setup_server", "arguments": {"backend": "in_repo", "landing_type": "thank_you_page", "payment_provider": "stripe"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• setup_status≈ 132 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "setup_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• setup_tracking≈ 322 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

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

  Exemple d'appel

  {"name": "setup_tracking", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• stage_conversion_installation≈ 429 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • digest · string · requis
  • bindings · array · requis
  • revision · integer · requis
  • generation · string · requis

  Exemple d'appel

  {"name": "stage_conversion_installation", "arguments": {"digest": "texte", "bindings": [], "revision": 1, "generation": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• start_signup≈ 324 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • client · string · optionnel · codex | cursor | claude_code | other
  • audit_id · string · optionnel
  • site_url · string · optionnel
    The customer's website (https) when there is no saved audit. The customer sees and approves it before connecting.
  • audit_key · string · optionnel
  • customer_approved · boolean · requis · True

  Exemple d'appel

  {"name": "start_signup", "arguments": {"customer_approved": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• submit_findings≈ 2646 tokens

  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.

  Paramètres, retour & exemple (19)

  Paramètres

  • url · string · requis
    the site these findings belong to
  • group · string · optionnel
    legacy grouping label only; does not combine reports or verify domain ownership
  • notes · ? · optionnel
    anything else found; a string or an array of strings
  • backend · string · optionnel · in_repo | separate_repo | unknown
    where the backend code is: in this repo, a separate repo not available here, or unknown
  • audit_id · string · optionnel
    audit run ID returned by Tyton; each audit run has its own ID
  • revision · integer · optionnel
    latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write
  • audit_key · string · optionnel
    private audit write capability returned by Tyton; a secret that authorizes changes to this audit only
  • dedup_ids · string · optionnel · yes | no | unknown
    orderId/event_id on both browser and server events?
  • framework · string · optionnel · nextjs | nuxt | astro | remix | sveltekit | vite | cra | plain_html
    frontend framework (from package.json deps)
  • request_id · string · optionnel
    UUID identifying one mutation; a repeated request_id with identical content is treated as a retry
  • existing_capi · object · optionnel
    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.g. v19.0), test_event_code_in_prod (is a test code left in production?), sends_fbp_fbc (are browser cookie values forwarded?)
  • pixel_in_code · string · optionnel · yes | no | unknown
    Meta Pixel initialized anywhere in the code?
  • not_applicable · array · optionnel
    Inapplicable checks, each with the actual reason, based on reviewed files and confirmed scope. Missing access counts as unknown, not N/A.
  • reviewed_files · array · optionnel
    relative paths actually inspected in the relevant customer repository; no source code, absolute paths or secret files
  • server_evidence · string · optionnel
    one line: file/function where it was found
  • checkout_domains · array · optionnel
    domains the checkout lives on, if separate; no customer paths or query strings
  • payment_provider · string · optionnel · stripe | lemonsqueezy | paddle | gumroad | shopify | polar | other | none
    payment processor used (from package.json, env vars, webhook routes)
  • container_in_code · string · optionnel · yes | no | unknown
    Tyton container script embedded?
  • server_side_events · string · optionnel · yes | no | unknown
    code sends server-side events (CAPI/SDK/webhook)? unknown when not checked

  Exemple d'appel

  {"name": "submit_findings", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "kind": "session", "source": "live_fetch", "status": "partial", "context": [], "session": {}, "decision": {}, "findings": [], "inventory": {}, "reportUrl": "texte", "capturedAt": "texte", "components": []}}

• tracking_status≈ 143 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "tracking_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_install≈ 185 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · requis
  • html · string · optionnel
    page HTML fetched by the agent

  Exemple d'appel

  {"name": "verify_install", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.usetyton.com/mcp