Manifest proof: the route map, policy fingerprint, approvals, examples and expected UI deltas are persisted in the target repository.
Chrome proof: a dedicated headed profile enumerates and executes each tool against the recorded secure verification origin.
-
Client proof: the exact client/account shows its supported subset of the page's registrations. In ChatGPT this surface is called Site tools; it currently discovers top-level imperative tools, not declarative forms or iframe registrations.
+
Client proof: the exact client/account shows its supported tools. In ChatGPT this surface is called Site tools; official documentation checked 2026-11-09 describes JavaScript registration, HTML forms and secure same-origin or cross-origin iframes. Account/workspace policy and provider-origin permissions still apply.
Additional read-only probe · 2026-11-09. Headed Chrome 156.0.8078.47 returned object callbacks as JSON text, strings as unquoted text, and absent values as the string undefined. The draft's scalar serialization rules differ; preserve raw evidence and explicit result guards. This browser did not expose outputSchema metadata. Schema declaration is not automatic output validation, and simulation does not prove native support. A document-replacement probe timed out; no document-lifetime or WPT conformance pass is claimed.
Last reviewed 2026-10-12. Chrome 149+ is the WebMCP origin-trial minimum; support for individual features depends on the browser version and must be verified. The synthetic Chrome Beta 156.0.8078.4 run on 2026-10-05 passed five native probes: object input, callback execution signal, cooperative caller cancellation, registration removal preserving a started invocation, and omitted input defaulting to {}. Successful imperative results arrived as serialized JSON strings. This does not prove declarative navigation, debugging annotations or every Chrome version. Chrome 150 required legacy JSON-string input and lacked callback options and omitted-input support; webmcpify probes with a side-effect-free tool before invoking any real tool, then executes each real tool exactly once.
The imperative API is a CG draft, not a finalized standard. Upstream PR #338 removed the declarative section on 2026-10-08; forms remain an experimental Chrome implementation described in the Chrome declarative guide and a separate explainer.
diff --git a/docs/site-tools/index.html b/docs/site-tools/index.html
index a1138a3..a8d9193 100644
--- a/docs/site-tools/index.html
+++ b/docs/site-tools/index.html
@@ -4,7 +4,7 @@
Use ChatGPT Site tools with WebMCP — webmcpify docs
-
+
@@ -23,7 +23,7 @@
ChatGPT calls WebMCP integrations Site tools. Treat the browser's own Available site tools list as ground truth for the page that is open right now.
PAGE-BOUND, MODEL-GATED
@@ -47,9 +47,9 @@
Requirements at this snapshot
Website: the page registers WebMCP from a secure context. Use HTTPS in production or a trustworthy loopback origin in development.
ChatGPT: update the desktop app, then open the website in its built-in browser.
-
Model: official OpenAI documentation checked 2026-10-12 lists GPT-5.6 Sol or GPT-6 Sol. GPT-5.6 Luna currently has WebMCP disabled.
-
Workspace: the official page requires an administrator to allow Site tools through Enterprise workspace policy; Edu is unavailable, and availability can also depend on rollout.
-
Client API: ChatGPT currently discovers imperative JavaScript tools in the top-level page. Declarative API form tools and tools registered inside iframes are not available as Site tools.
+
Model and access: a supported model and access through your account or managed workspace's browser policy are required. The current official page does not list model names or a workspace exclusion matrix; verify access in the exact account.
+
Permissions: browser settings and site permissions still apply. Check Enable site tools under Settings → Browser → Permissions.
+
Client API: the official page documents JavaScript tools and HTML form tools in the top-level page and same-origin or cross-origin iframes. Each frame needs a secure context; access is checked for the tool provider's origin.
@@ -67,9 +67,9 @@
Troubleshoot in this order
Symptom
Check
Meaning
No Site tools control
Desktop-app version, selected model, workspace and rollout.
The client surface may be unavailable before the site is involved.
-
Control exists, expected tool absent
Available site tools while the exact page is open; then top-level imperative registration and secure context.
The page did not register it in the current document, registration failed, or it uses a declarative form or iframe that this client does not discover.
+
Control exists, expected tool absent
Available site tools while the exact page is open; registration or form metadata, frame secure context and provider-origin access.
Check document lifetime, registration errors and permissions rather than assuming iframe or form tools are unsupported.
Tool worked, then vanished
Did the browser close, navigate, reload or replace the page between turns?
Tools belong to their page; page teardown ends that registration.
-
Assistant uses ordinary browser interaction
Confirm GPT-5.6 Sol or GPT-6 Sol plus Work or Codex and inspect Available site tools directly.
Fallback browser behavior can look like a broken integration.
+
Assistant uses ordinary browser interaction
Confirm a supported model, account/workspace access and browser permissions; inspect Available site tools directly.
Fallback browser behavior can look like a broken integration.
Tool call is held or asks for confirmation
Review the requested action and client safety result.
Every invocation receives a client-side safety review; normal confirmation policy still applies.
@@ -102,7 +102,7 @@
FAQ
Does every tool that works in Chrome appear as a Site tool?
-
No. As checked 2026-10-12, ChatGPT's built-in browser supports imperative tools registered in the top-level page, but not declarative form tools or registrations inside iframes. Regular browser interaction may still operate those forms.
+
No account-level compatibility promise follows from a Chrome test. The official guide checked 2026-11-09 documents JavaScript registration, HTML forms and secure same-origin or cross-origin iframes. Verify the actual account, provider-origin permissions and Available site tools list.
What about plain Chat or a Work workspace?
@@ -112,11 +112,11 @@
FAQ
Sources and date boundary
-
OpenAI: Site tools, checked 2026-10-12 for naming, model/workspace availability, supported API subset, controls, page lifetime and safety review.
-
WebMCP draft, dated 2026-08-26, for the secure-context Document API.
+
OpenAI: Site tools, checked 2026-11-09 for account/workspace policy, form/frame discovery, controls, page lifetime and safety review. This is a documentation check, not a live account test.
+
WebMCP draft, dated 2026-11-02, for the secure-context Document API.
Re-check these pages before copying model names or workspace claims into another public surface.
+
The official guide permits omitting exposedTo for agent discovery. This is distinct from in-page cross-origin discovery, which still requires embedder delegation, provider exposure and consumer opt-in. Re-check the primary sources before publishing availability claims.
diff --git a/llms.txt b/llms.txt
index f7c63e1..d6203d8 100644
--- a/llms.txt
+++ b/llms.txt
@@ -33,7 +33,7 @@ Important boundaries:
- [WebMCP proposal](https://webmachinelearning.github.io/webmcp/): W3C Web Machine Learning Community Group draft for page-provided tools.
- [Chrome WebMCP documentation](https://developer.chrome.com/docs/ai/webmcp): Current Chrome origin-trial and implementation guidance.
-- [Using Site tools in ChatGPT](https://webmcpify.at/docs/site-tools/): Dated setup and troubleshooting guide. As checked on 2026-10-12, ChatGPT discovers top-level imperative JavaScript tools, not Declarative API forms or registrations inside iframes; availability varies during rollout.
+- [Using Site tools in ChatGPT](https://webmcpify.at/docs/site-tools/): Official documentation checked 2026-11-09 describes JavaScript registration, HTML forms and secure same-origin/cross-origin iframes; account/workspace policy and provider-origin permissions still apply. Documentation evidence is separate from account verification.
- [Official ChatGPT Site tools documentation](https://learn.chatgpt.com/docs/webmcp): Primary source for supported models, accounts, discovery, lifetime, and safety review.
## Optional
diff --git a/tests/pages.test.mjs b/tests/pages.test.mjs
index 184c92d..e92d6cb 100644
--- a/tests/pages.test.mjs
+++ b/tests/pages.test.mjs
@@ -158,20 +158,19 @@ test('the Site tools guidance stays dated, scoped and linked to the official sou
for (const fact of [
'Site tools',
'Available site tools',
- '2026-10-12',
- 'GPT-5.6 Sol',
- 'GPT-6 Sol',
- 'Luna',
- 'Enterprise',
- 'Edu',
+ '2026-11-09',
+ 'supported model',
+ 'browser policy',
'safety review',
- 'Declarative API',
+ 'HTML form',
'iframes',
'top-level page',
]) {
assert.ok(html.includes(fact), `${page} is missing dated Site tools fact: ${fact}`);
}
assert.ok(html.includes(official), `${page} must cite the official Site tools guide`);
+ assert.doesNotMatch(html, /GPT-5\.6 Sol|GPT-6 Sol|Edu is unavailable|not Declarative API/,
+ `${page} must not retain the superseded availability matrix`);
assert.match(
html,
/(?:keep (?:the )?(?:target )?page open|keep its browser tab open|page (?:stays|remains) open)/i,
@@ -180,7 +179,7 @@ test('the Site tools guidance stays dated, scoped and linked to the official sou
}
const machineSummary = normalize(read('llms.txt'));
- for (const fact of ['2026-10-12', 'top-level imperative', 'Declarative API', 'iframes']) {
+ for (const fact of ['2026-11-09', 'HTML forms', 'cross-origin', 'provider-origin']) {
assert.ok(machineSummary.includes(fact), `llms.txt is missing Site tools boundary: ${fact}`);
}
assert.ok(machineSummary.includes(official), 'llms.txt must cite the official Site tools guide');
diff --git a/webmcp-agent-skill/index.html b/webmcp-agent-skill/index.html
index 08243cc..996da9e 100644
--- a/webmcp-agent-skill/index.html
+++ b/webmcp-agent-skill/index.html
@@ -297,10 +297,10 @@
Using the result in ChatGPTDas Ergebn
ChatGPT calls WebMCP integrations Site tools. In the desktop app's built-in browser, keep the page open, select Site tools in the address bar, then open Available site tools. That list is the fastest client-side answer to “did this page register?”.ChatGPT nennt WebMCP-Integrationen Site tools. Lass die Seite im integrierten Browser der Desktop-App geöffnet, wähle Site tools in der Adressleiste und öffne Available site tools. Diese Liste beantwortet clientseitig am schnellsten: „Hat diese Seite registriert?“
-
Model and account: official OpenAI documentation checked 2026-10-12 lists GPT-5.6 Sol or GPT-6 Sol; Luna has WebMCP disabled. Enterprise requires an administrator to allow Site tools through workspace policy; Edu is unavailable, and rollout still varies.
- Modell und Konto: Die am 12.10.2026 geprüfte offizielle OpenAI-Dokumentation nennt GPT-5.6 Sol oder GPT-6 Sol; bei Luna ist WebMCP deaktiviert. In Enterprise muss ein Administrator Site tools per Workspace-Richtlinie erlauben; Edu ist nicht verfügbar, und der Rollout kann variieren.
-
Client coverage: Site tools currently discover imperative JavaScript tools in the top-level page, not Declarative API form tools or registrations inside iframes.
- Client-Abdeckung: Site tools erkennen derzeit imperative JavaScript-Tools in der Top-Level-Seite, nicht Tools der Declarative API auf Formularen oder Registrierungen in iframes.
+
Model and account: official documentation checked 2026-11-09 requires a supported model and access through your account or managed workspace's browser policy. It does not list model names or workspace exclusions; check the actual account and browser permissions.
+ Modell und Konto: Die am 09.11.2026 geprüfte offizielle Dokumentation verlangt ein unterstütztes Modell und Zugriff über das Konto oder die Browser-Richtlinie des verwalteten Workspace. Modellnamen und Workspace-Ausschlüsse werden nicht aufgelistet; prüfe das konkrete Konto und die Browser-Berechtigungen.
+
Client coverage: the guide documents JavaScript tools and HTML forms in the top-level page and same-origin or cross-origin iframes. Every frame needs a secure context; access is checked for the tool provider's origin.
+ Client-Abdeckung: Der Leitfaden beschreibt JavaScript-Tools und HTML-Formulare in der Hauptseite sowie gleich- und fremdoriginären iframes. Jeder Frame braucht einen sicheren Kontext; der Zugriff wird für die Herkunft des Tools geprüft.
Page lifetime: tools belong to the open page. Closing or navigating away can make them unavailable between turns.Seiten-Lebensdauer: Tools gehören zur geöffneten Seite. Schließen oder Wegnavigieren kann sie zwischen Turns unverfügbar machen.
Safety: every invocation receives a client-side safety review; normal access and confirmation policies still apply.
@@ -312,8 +312,8 @@
FAQ
Why do Site tools look missing in ChatGPT?Warum wirken Site tools in ChatGPT verschwunden?
-
Check the page's Available site tools list first, then top-level imperative registration, the current desktop-app version, supported model and workspace availability. Site tools die with the page, so keep its browser tab open. Chrome verification and ChatGPT account availability are separate checks.
- Prüfe zuerst die Liste Available site tools der Seite, dann die imperative Registrierung auf der Top-Level-Seite, die aktuelle Desktop-App, ein unterstütztes Modell und die Workspace-Verfügbarkeit. Site tools sterben mit der Seite; lass ihren Browser-Tab offen. Chrome-Verifikation und ChatGPT-Kontoverfügbarkeit sind getrennte Prüfungen.
+
Check the page's Available site tools list first, then registration or form metadata, each frame's secure context, provider-origin permissions and account/workspace access. Site tools belong to the page, so keep its browser tab open. Chrome verification and ChatGPT account availability are separate checks.
+ Prüfe zuerst Available site tools, dann Registrierung oder Formular-Metadaten, den sicheren Kontext jedes Frames, Berechtigungen der Tool-Herkunft und Konto-/Workspace-Zugriff. Site tools gehören zur Seite; lass den Browser-Tab offen. Chrome-Verifikation und ChatGPT-Kontoverfügbarkeit sind getrennte Prüfungen.
Which agents can run this skill?Welche Agents können diesen Skill ausführen?