Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Tyton is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
27
tools declared
remote
at its publisher
—
calls last 7d
What it does
Audit and set up Meta Pixel and the Conversions API from your AI agent.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http tyton-mcp https://mcp.usetyton.com/mcp
# 2 — ask your agent for something these tools do
# start_signup, get_signup_status, delete_connected_project and 24 more
Tyton costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 1 server
usetyton1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http tyton-mcp https://mcp.usetyton.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
27 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 pi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audit_id | string | no | — |
| audit_key | string | no | — |
| site_url | string | no | The customer's website (https) when there is no saved audit. The customer sees and approves it before connecting. |
| customer_approved | boolean | yes | — |
| client | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | — |
| poll_token | string | yes | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| confirmed | boolean | yes | — |
| expected_url | string | yes | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pixel_id | string | yes | — |
| capi_token | string | no | — |
| sealed_capi_token | string | no | A sealed token from the Tyton browser extension, exactly as given (starts with tyton_sealed_v1.). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_url | string | yes | — |
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.
No parameter schema on file.
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| installation_id | string | yes | — |
| events | array | yes | — |
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.
No parameter schema on file.
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 on
| Parameter | Type | Required | Notes |
|---|---|---|---|
| revision | integer | yes | — |
| digest | string | yes | — |
| confirmed | boolean | yes | — |
| customer_confirmation | object | yes | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| revision | integer | yes | — |
| digest | string | yes | — |
| request_id | string | yes | — |
| confirmed | boolean | yes | — |
| customer_confirmation | object | yes | — |
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 cann
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| revision | integer | yes | — |
| digest | string | yes | — |
| generation | string | yes | — |
| bindings | array | yes | — |
Reads the connected site's current conversion plan draft, its open questions, approval state and review link. Read-only.
No parameter schema on file.
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. Off
| Parameter | Type | Required | Notes |
|---|---|---|---|
| expected_revision | integer | yes | — |
| request_id | string | yes | — |
| document | object | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audit_id | string | yes | — |
| audit_key | string | yes | — |
| revision | integer | no | latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write |
| request_id | string | no | UUID identifying one mutation; a repeated request_id with identical content is treated as a retry |
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 ac
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audit_id | string | no | audit run ID returned by Tyton; each audit run has its own ID |
| audit_key | string | no | private audit write capability returned by Tyton; a secret that authorizes changes to this audit only |
| revision | integer | no | latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write |
| request_id | string | no | UUID identifying one mutation; a repeated request_id with identical content is treated as a retry |
| url | string | yes | — |
| answers | object | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audit_id | string | no | audit run ID returned by Tyton; each audit run has its own ID |
| audit_key | string | no | private audit write capability returned by Tyton; a secret that authorizes changes to this audit only |
| revision | integer | no | latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write |
| request_id | string | no | UUID identifying one mutation; a repeated request_id with identical content is treated as a retry |
| url | string | yes | — |
| observed_at | string | yes | — |
| consent_state | string | yes | — |
| checks | array | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | the pairing code, e.g. 7K2M-QX4T (dashes optional) |
| client | string | no | which host is calling; used to label the new key |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audit_id | string | no | audit run ID returned by Tyton; each audit run has its own ID |
| audit_key | string | no | private audit write capability returned by Tyton; a secret that authorizes changes to this audit only |
| revision | integer | no | latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write |
| request_id | string | no | UUID identifying one mutation; a repeated request_id with identical content is treated as a retry |
| url | string | yes | the site to audit |
| html | string | no | 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 pr |
| fresh | boolean | no | bypass the short public-page cache when verifying a change |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | the site being tracked: a domain or full URL |
| pixel_id | string | no | Meta Pixel ID, numeric; optional while it is not yet known |
| name | string | no | project name; defaults to the site name |
| checkout_domains | array | no | hostnames where checkout happens, if already known |
| confirm_change | boolean | no | true = yes, switch this project to a different Pixel ID or site URL on purpose |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| payment_provider | string | yes | who processes payments, as shown in code (package.json, env vars, webhook routes) |
| landing_type | string | yes | 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 | no | e.g. /checkout/success or /dashboard; applies only to thank_you_page and app_route |
| landing_marker | string | no | what marks a purchase in the landing URL, e.g. ?checkout=success; often empty |
| backend | string | yes | where server code runs, as shown by the code (api, server or functions directories, or a separate service) |
| checkout_domains | array | no | hostnames checkout lives on, if not the site itself ([] clears what's stored) |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | — |
| html | string | no | page HTML fetched by the agent |
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.
No parameter schema on file.
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 behavi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audit_id | string | no | audit run ID returned by Tyton; each audit run has its own ID |
| audit_key | string | no | private audit write capability returned by Tyton; a secret that authorizes changes to this audit only |
| revision | integer | no | latest run revision; 0 for the first write of a new audit session, then the revision returned by the previous write |
| request_id | string | no | UUID identifying one mutation; a repeated request_id with identical content is treated as a retry |
| url | string | yes | the site these findings belong to |
| reviewed_files | array | no | relative paths actually inspected in the relevant customer repository; no source code, absolute paths or secret files |
| not_applicable | array | no | Inapplicable checks, each with the actual reason, based on reviewed files and confirmed scope. Missing access counts as unknown, not N/A. |
| server_side_events | string | no | code sends server-side events (CAPI/SDK/webhook)? unknown when not checked |
| server_evidence | string | no | one line: file/function where it was found |
| dedup_ids | string | no | orderId/event_id on both browser and server events? |
| pixel_in_code | string | no | Meta Pixel initialized anywhere in the code? |
| container_in_code | string | no | Tyton container script embedded? |
| payment_provider | string | no | payment processor used (from package.json, env vars, webhook routes) |
| framework | string | no | frontend framework (from package.json deps) |
| backend | string | no | where the backend code is: in this repo, a separate repo not available here, or unknown |
| existing_capi | object | no | 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. |
| checkout_domains | array | no | domains the checkout lives on, if separate; no customer paths or query strings |
| group | string | no | legacy grouping label only; does not combine reports or verify domain ownership |
| notes | no | anything else found; a string or an array of strings |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | — |
| step | string | no | Optional Meta setup step; only used with topic meta_setup. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Tyton or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 3 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestb827b7490f45608695d23a1abb756b61e1fb785230cda0cf2786ccb6d2e5599d
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| start_signup | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_signup_status | no tags | |
| delete_connected_project | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| save_capi_token | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| save_audit_to_project | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_setup_progress | no tags | |
| check_live_setup | no tags | |
| get_sdk_installation | untrusted-input | untrusted-input: keyword "download" |
| approve_conversion_plan | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| approve_and_start_conversion_plan | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| read_conversion_installation | no tags | |
| stage_conversion_installation | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| read_conversion_plan | no tags | |
| propose_conversion_plan | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| begin_audit | no tags | |
| read_audit | no tags | |
| record_audit_context | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| record_audit_runtime | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| connect | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| audit_site | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| setup_tracking | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| setup_server | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| setup_status | no tags | |
| verify_install | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| tracking_status | no tags | |
| submit_findings | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| read_docs | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestb827b7490f456086
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Tyton can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.