=== AGENT LAYER · two-tier/2.0.0 · structured equivalent of this page · markdown twin: https://mahoneycontextprotocol.com/index.html.md === ```yaml spec: two-tier/2.0.0 id: mcp-home type: Organization date_modified: "2026-06-11" facts: name: Mahoney Context Protocol email: "joe@joemahoney.io" tagline: Make any site agent-native — and prove it. thesis: The two-tier web — presentation layer + agent-surface layer — where the layer you read tells you the site can be operated, and the layer an agent uses backs that up with a live handshake. sections: [layers, orchestrator, presence, contact, machine] tools: - name: get_context description: Returns structured context about Mahoney Context Protocol — name, email, tagline, thesis (two-tier web), and blog URL. input_schema: type: object properties: {} output_schema: type: object properties: name: {type: string} email: {type: string} mailto: {type: string} tagline: {type: string} thesis: {type: string} blog_url: {type: string} - name: search_blog description: >- Searches blog posts by keyword. Static search on available posts. Returns matching posts with title, URL, and excerpt. Static site, no backend — submitted: false. input_schema: type: object properties: query: type: string description: Keyword or phrase to search for in blog posts required: [query] output_schema: type: object properties: query: {type: string} matches: type: array items: type: object properties: title: {type: string} url: {type: string} excerpt: {type: string} submitted: {const: false} conformance: conneg: static-fallback capabilities: [content-signals] ```

Make any site agent-native — and prove it.

Mahoney Context Protocol builds the layer of a website that AI agents read, then verifies it with a probe that runs the handshake — not a badge that checks a box.

Two layers, one site

Presentation layerWhat a person sees: the design, the words, the page. It advertises that the site can be operated.

Agent-surface layerWhat an agent uses: a working MCP server card, an A2A card, WebMCP tools, Agent Skills, OAuth discovery, schemas, an OpenAPI catalog — that actually answer when an agent knocks.

The two reinforce each other: the layer you read tells you the site can be operated, and the layer an agent uses backs that up with a live handshake.

The orchestrator

One manifest as the source of truth. Twenty generators for the machine layer. A probe gate between every step, so the chain can't move forward until the last thing it built actually handshakes. It takes a bare domain to agent-native, then re-scans to prove it — with a connection, not a checkmark.

Why presence isn't enough

Presence is cheap. A site can declare its whole agent surface in Link headers and have every path behind them return 404. Presence is a costume. The handshake is the test.

Read: Your AI-readiness badge is lying →

Mahoney Context Protocol

Make any site agent-native — and prove it.

Context

Name: Mahoney Context Protocol
Email: joe@joemahoney.io
Tagline: Make any site agent-native — and prove it.
Thesis: The two-tier web: presentation layer (what humans read) + agent-surface layer (what agents use). One manifest as the source of truth. Twenty generators for the machine layer. A probe gate between every step.
Blog: Your AI-readiness badge is lying

Agent tools

get_context() Returns structured context: name, email, tagline, thesis, blog URL

search_blog({ query }) Search blog posts by keyword (static search on available posts)

Make any site agent-native — and prove it.

Two layers, one site

The orchestrator

Why presence isn't enough

Mahoney Context Protocol

Context

Agent tools

Agent surfaces