Skip to content

Tyton MCP server

com.usetyton/tytonusetyton.comstreamable-httpv1.0.0Scanned

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

27 tools: 15 can delete or cancel things, 3 change things and 9 only read.

Tools: 15 delete, 0 irreversible, 3 write, 9 read.
  • Reads private data · 2
  • Reads text others write · 6
  • Can send data out · 2
  • 4 findings

Tools listed without sign-in. Remote posture

With Anlyon

15 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Tyton MCP server can do

The Tyton MCP server is published by usetyton.com, a domain the MCP Registry verified. It has 27 tools. It can delete or cancel things (15 tools: start_signup, delete_connected_project, save_capi_token, save_audit_to_project and 11 more) and create or change data (3 tools: check_live_setup, begin_audit and verify_install). 9 tools only read.

2 tools read private data (get_sdk_installation and read_docs); 6 tools bring in text other people can write (save_capi_token, read_conversion_plan, audit_site and 3 more); 2 tools can send data out of your system (begin_audit and verify_install). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 4 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

27 tools

Deletes or cancels 15Claude Code: deny
  • approve_and_start_conversion_planRecords 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 i…No findings

    Why it is in this group

    • The name "approve_and_start_conversion_plan" says "approve": a word for a change.
    • The name "approve_and_start_conversion_plan" also says "start": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Approve plan and request start
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • approve_conversion_planRecords approval of an unchanged conversion plan proposal, identified by its revision and digest, after the customer explicitly accepted it in chat.No findings

    Why it is in this group

    • The name "approve_conversion_plan" says "approve": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Approve conversion plan
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • audit_siteInspects one public page's HTML and saves a partial audit report, without signup.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "inspect": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "inspect" and "html": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Audit a public page
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • connectConnects a Tyton site to this connection using a single-use pairing code from the site's card on usetyton.com (valid for 15 minutes).No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Connect with pairing code
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • delete_connected_projectPermanently deletes the Tyton project connected to this connection, including its keys, setup and stored event history.No findings

    Why it is in this group

    • The name "delete_connected_project" says "delete": a word for removing or ending something.
    • The description says "Permanently deletes".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Delete connected site
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • propose_conversion_planSaves a conversion plan draft for the connected site.No findings

    Why it is in this group

    • The description's first verb is "save": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Draft conversion plan
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • record_audit_contextSaves answers about one audited component to the audit.No findings

    Why it is in this group

    • The description's first verb is "save": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Record audit answers
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • record_audit_runtimeSaves 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 obse…1 finding

    Why it is in this group

    • The description's first verb is "save": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.checks.items.properties.evidence.description mentions "credentials".

      Matched text

      inputSchema.properties.checks.items.properties.evidence.description: "...ation, without payloads, identifiers or credentials"

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Record runtime evidence
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • save_audit_to_projectLinks an existing Tyton audit report to the connected website's Get Started checklist.No findings

    Why it is in this group

    • The name "save_audit_to_project" says "save": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Link audit to site
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • save_capi_tokenSaves a Meta Conversions API token for the connected site's current Pixel.Reads text others writeNo findings

    Why it is in this group

    • The name "save_capi_token" says "save": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Save Conversions API token
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • setup_serverSaves checkout and landing answers (payment provider, landing type and route, checkout domains) for the connected project and returns the reviewed server SDK success-callback contr…No findings

    Why it is in this group

    • The description's first verb is "save": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Save server setup answers
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • setup_trackingDiscovers or configures reviewed v2 setup for a site.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Discover or configure site
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • stage_conversion_installationStages callback bindings (conversion, target and a browser or server source) for the approved latest plan revision and digest under an installation generation.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Stage installation
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • start_signupCreates a Tyton signup and Connect link for one website.No findings

    Why it is in this group

    • The name "start_signup" says "start": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create signup link
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • submit_findingsSaves 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 a…No findings

    Why it is in this group

    • The name "submit_findings" says "submit": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Submit code findings
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 3Claude Code: ask
  • begin_auditStarts a new free audit session for a URL.Can send data out1 finding

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "begin_audit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Begin free audit
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_live_setupChecks whether specific PageView or conversion event IDs from an activated live installation reached Tyton's dashboard storage in the last 24 hours.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check live event receipts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • verify_installChecks 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.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "verify_install" says "install": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "verify_install" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "verify_install" says "install": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check page HTML for Pixel
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 9Show 9 read-only tools
  • get_sdk_installationReturns the private Tyton server SDK download, its SHA-256 checksum and the local-file install steps for the connected project.Reads private dataNo findings

    Why it is in this group

    • The name "get_sdk_installation" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "file": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get SDK install instructions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_setup_progressReads the connected site's setup state in one compact response: plan approval, installation generation, missing callback sources, intentional pauses and the single next step.1 finding

    Why it is in this group

    • The name "get_setup_progress" says "get": a word for reading.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...ification-only setup works without Meta credentials. Requires a connected site."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read setup progress
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_signup_statusChecks a signup and Connect request using its request_id and private poll_token.No findings

    Why it is in this group

    • The name "get_signup_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check signup status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_auditReads an existing audit using its private capability.No findings

    Why it is in this group

    • The name "read_audit" says "read": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read audit
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_conversion_installationReads staged callback bindings, observed verification signals and the active or paused installation state for the connected site.No findings

    Why it is in this group

    • The name "read_conversion_installation" says "read": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read installation state
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_conversion_planReads the connected site's current conversion plan draft, its open questions, approval state and review link.Reads text others writeNo findings

    Why it is in this group

    • The name "read_conversion_plan" says "read": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "read" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    Reads the connected site's current conversion plan draft, its open questions, approval state and review link. Read-only.

    Annotations the server declares

    • title: Read conversion plan
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_docsReturns Tyton guidance on one topic.Reads private dataNo findings

    Why it is in this group

    • The name "read_docs" says "read": a word for reading.

    What it can reach

    • private-dataThe name "read_docs" says "read" and "doc": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read Tyton guidance
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • setup_statusReads the connected project's configuration: site URL, Pixel ID, token status and saved checkout answers.Reads text others writeNo findings

    Why it is in this group

    • The name "setup_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "read" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read site configuration
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • tracking_statusReads aggregate browser and server event observations, delivery statuses, and the known-crawler protection mode and counts for the connected site.Reads text others writeNo findings

    Why it is in this group

    • The name "tracking_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "read" and "browser": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read tracking status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

24 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__tyton__begin_audit",
      "mcp__tyton__verify_install"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:49 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
18
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.usetyton.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://usetyton.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 18 tools that change things (15 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.usetyton.com/mcp: tools/list returned 27 tools to an anonymous client, including start_signup (destructive), delete_connected_project (destructive), save_capi_token (destructive), save_audit_to_project (destructive), approve_conversion_plan (destructive) and 13 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn2 info
  • The server marks "begin_audit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.

    What this check looks for
  • The server marks "verify_install" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "verify_install" says "install": a word for a change.

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...ification-only setup works without Meta credentials. Requires a connected site."

    What this check looks for
  • The input schema at properties.checks.items.properties.evidence.description mentions "credentials".

    Matched text

    inputSchema.properties.checks.items.properties.evidence.description: "...ation, without payloads, identifiers or credentials"

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tyton__get_signup_status",
      "mcp__tyton__get_setup_progress",
      "mcp__tyton__get_sdk_installation",
      "mcp__tyton__read_conversion_installation",
      "mcp__tyton__read_conversion_plan",
      "mcp__tyton__read_audit",
      "mcp__tyton__setup_status",
      "mcp__tyton__tracking_status",
      "mcp__tyton__read_docs"
    ],
    "ask": [
      "mcp__tyton__check_live_setup",
      "mcp__tyton__begin_audit",
      "mcp__tyton__verify_install"
    ],
    "deny": [
      "mcp__tyton__start_signup",
      "mcp__tyton__delete_connected_project",
      "mcp__tyton__save_capi_token",
      "mcp__tyton__save_audit_to_project",
      "mcp__tyton__approve_conversion_plan",
      "mcp__tyton__approve_and_start_conversion_plan",
      "mcp__tyton__stage_conversion_installation",
      "mcp__tyton__propose_conversion_plan",
      "mcp__tyton__record_audit_context",
      "mcp__tyton__record_audit_runtime",
      "mcp__tyton__connect",
      "mcp__tyton__audit_site",
      "mcp__tyton__setup_tracking",
      "mcp__tyton__setup_server",
      "mcp__tyton__submit_findings"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tyton. Review it before you use it.

Capability tags behind 9 rules
  • mcp__tyton__save_capi_token untrusted-input
  • mcp__tyton__get_sdk_installation private-data
  • mcp__tyton__read_conversion_plan untrusted-input
  • mcp__tyton__begin_audit outbound
  • mcp__tyton__audit_site untrusted-input
  • mcp__tyton__setup_status untrusted-input
  • mcp__tyton__verify_install untrusted-input, outbound
  • mcp__tyton__tracking_status untrusted-input
  • mcp__tyton__read_docs private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.usetyton/tyton/verify?hash=777267a0b8755db49c22ce9ef7fd6d077d90d7cc7bb3a515f7cec1523e723590" | jq -e '.changed == false'

Pinned hash 777267a0b875, from Nov 11, 2026, 05:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.usetyton/tyton/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.usetyton/tyton
[![Anlyon Radar](https://radar.anlyon.com/badge/com.usetyton/tyton.svg)](https://radar.anlyon.com/servers/com.usetyton/tyton)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:10 UTC.

Tyton MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Tyton MCP server safe?

No scan can promise that. What its definitions show: 27 tools, 18 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Tyton MCP server delete data?

Yes. 15 tools can delete, cancel or revoke something: start_signup, delete_connected_project, save_capi_token, save_audit_to_project, approve_conversion_plan, approve_and_start_conversion_plan and 9 more.

Can the Tyton MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Tyton MCP server have?

27 tools: 15 destructive, 3 write, 9 read. start_signup, delete_connected_project, save_capi_token, save_audit_to_project, approve_conversion_plan, approve_and_start_conversion_plan, stage_conversion_installation, propose_conversion_plan and 19 more.

Does the Tyton MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Tyton MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): begin_audit and verify_install.

Has the Tyton MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.