In short
- webMCP is not free access to internal systems.
- It describes profiles, rules, functions and endpoints.
- For businesses, control and routing stay central.
Not everything is open
The key point: webMCP does not mean agents can access everything freely. It means allowed things are clearly described.
An agent can read which functions exist. Private data, internal notes and recipient addresses stay hidden.
Why a manifest helps
A manifest like /.well-known/webmcp.json can show agents which profiles, files, APIs and contact paths exist.
It's like a technical map. It doesn't say everything about the business, but it shows where reliable information and allowed actions live.
How agentready.ch uses it
agentready.ch combines webMCP, OpenAPI, MCP tools, agent.json, agent.md and llms.txt into a single agent layer.
The goal is a bridge: businesses stay reachable under control, agents get clear rules.
Checklist
- Publish a manifest
- Keep the Agent Index current
- Maintain functions with clear descriptions
- Don't publish private routing data
- Keep OpenAPI and MCP consistent
Frequently asked
Is webMCP an official standard?
At agentready.ch, webMCP is a practical implementation idea for the agentic web. It follows MCP and OpenAPI principles but doesn't replace a security review.
Why not just a contact form?
Contact forms are for people. Agents additionally need structured descriptions of actions, parameters, rules and delivery.
Ask Google AI
Ask ChatGPT
Ask Claude