Tool contract
Read the four-tool contract and bounds
search_site, get_page_content, list_content, and get_sitemap.
WebMCP use-case gallery
Corsen Context — WebMCP Demo
Corsen Context gives a site an explicit, owner-governed read path for agents — four read-only tools served over MCP and registered in-page through WebMCP.
This is a live deployment of the Corsen Context static-HTML example, served from one origin with the same four read-only tools.
Try with your agent
Three copyable research prompts
Copy any prompt into your agent. The page does not simulate an answer or perform an action on your behalf.
What is Corsen Context and which four read-only tools does it publish?Compare the integration stacks and tell me which one fits a static HTML site.Find the WebMCP browser setup guide and list the current requirements.
Different retrieval patterns
A gallery of real content workflows
Support
Retrieve a fixed diagnostic sequence
Three ordered checks and one stop-and-escalate rule for MCP-404.
Security
Review the four guarantees
Read-only, same-origin, rate-limited, and bounded.
Guides
Browse six dated guides
WebMCP setup, MCP vs WebMCP, install, security, stacks, and llms.txt.
For site owners
Replace the demo records with your content.
The human pages and all four tools read from the same records, so URLs and answers stay aligned.