Does the plugin let agents write to my site?
The core contract is read-only: search_site, get_page_content, list_content and get_sitemap never create, edit, delete or purchase anything. The optional extensions are read-only too, with one deliberate exception: request_expert_call is annotated non-read-only and is human-only. Every schema-valid agent invocation is refused server-side with the error code human_only before anything is stored or emailed, and the agent receives the page URL so a person can use the visible form.
Can an agent buy something in the demo store?
Only what the owner allows, product by product. When the get_product extension is enabled, every product carries agentPurchase: allowed or forbidden with a reason. On allowed, an agent acting for its user may add the product to the cart and complete the ordinary checkout, including creating the customer account it requires. On forbidden — the flagship edition on this site — it must not start checkout and hands the product URL to a human. This is a binding instruction in the agent contract; Corsen Context exposes no purchase tool and does not intercept the human checkout.
What can I exclude?
Whole post types, individual paths, and anything the exposure filter vetoes. Drafts, private and password-protected posts, and WooCommerce transactional pages (cart, checkout, account) are never exposed, even when the page post type is selected.
Why structuredContent?
Agents get typed JSON they can validate — prices as numbers, stock as booleans, URLs as URLs — instead of a string of Markdown to re-parse. Text results are kept for clients that only read content.
Can I see what agents did?
The opt-in audit log records timestamp, tool, an argument fingerprint, a hashed IP prefix, the outcome and the duration. Raw arguments and raw addresses are never stored, and the log is bounded and purgeable from the Control Center.
Which browsers and clients support WebMCP?
WebMCP is an experimental browser API. Today it works in ChatGPT’s in-app browser and in Chrome 149 or newer with the enable-webmcp-testing flag; public origin trials are origin-specific and expire. Serving the bridge is necessary but not sufficient: the browser must expose document.modelContext and an agent must consume the registered tools. The MCP endpoint and /llms.txt work with any HTTP client regardless of the browser.
Is the contract hash a security proof?
No. It proves that the same four-tool contract is deployed across the ten stacks — identity, not safety. Safety comes from bounded schemas, server-side validation, owner switches and fail-closed defaults.
What does it cost?
Corsen Context is open source under the MIT license: the plugin, the npm packages and every reference integration are free to use, commercially or not. The store on this site is a demonstration of product governance; nothing is shipped and no payment is processed.
Where is the code?
The canonical monorepo is github.com/CorsenAI/corsen-context; each integration also has a standalone repository listed on the Integrations page.