# How This Site Is Agent-Native: WebMCP, MCP, llms.txt

> This site practices what it teaches. It exposes the same content and tools through seven surfaces so an agent can find it, read it, and act on it. The content is public and read-only, so none of the surfaces need authentication. A product that changes state would add the scoped-authority layer on top.

URL: https://agentnative.build/agents · By Mark Hinkle · Updated 2026-10-21
Machine-readable index: https://agentnative.build/llms.txt

## What surfaces does this site expose to agents?

> Seven: an llms.txt index, a single-file llms-full.txt, Markdown twins of every page, Markdown content negotiation on the normal URLs, a remote MCP server, WebMCP tools registered in the page, and JSON-LD structured data.

| Surface | Where | What an agent gets |
|---|---|---|
| llms.txt | /llms.txt | A short index of pages, one line each |
| llms-full.txt | /llms-full.txt | The whole site as one Markdown file, for a single fetch |
| Markdown twins | /index.md, /future.md, /examples.md, /agents.md | Each page as clean Markdown |
| Content negotiation | Any page with `Accept: text/markdown` | The same URL, answered as Markdown |
| Remote MCP server | /api/mcp | Five read-only tools over JSON-RPC |
| WebMCP tools | In the page, via `navigator.modelContext` | The same tools plus reader-view and navigation control, for browser agents |
| Structured data | JSON-LD in each page head | Article, FAQPage, and BreadcrumbList |

## What is the difference between llms.txt and llms-full.txt?

> llms.txt is a short Markdown index that tells a model which pages exist and where to find clean versions. llms-full.txt carries the full content inline, so an agent can load the entire site in one request.

Both are community conventions, not standards. Support from search engines and model providers is not confirmed, so treat them as a low-cost courtesy to agents and developer tools that do read them, not as a ranking lever.

## Which WebMCP tools does this page register?

> When the browser exposes the WebMCP API, the page registers seven tools. Five mirror the MCP server and two control the page itself. If the API is absent, nothing is registered and the page works as normal.

- `get_definition`: the definition of agent-native software.
- `list_principles`: the eight design principles with bolted-on and native examples.
- `score_product`: takes twelve yes or no answers and returns the score, tier, and the gaps to close.
- `get_page`: any page as Markdown.
- `search_site`: keyword search across every page.
- `set_reader_view`: switch the page between the human view and the agent view.
- `open_page`: navigate to a page on this site.

> **Status.** WebMCP is a draft proposal. The entry point has shifted between drafts, so the page checks for both `navigator.modelContext` and `document.modelContext` and registers nothing if neither exists.

## How do I call the MCP server?

> Send JSON-RPC 2.0 over HTTP POST to https://agentnative.build/api/mcp. Every request is self-contained: there is no session, and no handshake is required before calling a tool.

*List the tools*

```
curl -s https://agentnative.build/api/mcp   -H 'content-type: application/json'   -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

*Score a product (first four answers yes)*

```
curl -s https://agentnative.build/api/mcp   -H 'content-type: application/json'   -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{
    "name":"score_product",
    "arguments":{"answers":[true,true,true,true,false,false,false,false,false,false,false,false]}}}'
```

## How does Markdown content negotiation work?

> Request any page with an Accept header that prefers text/markdown and the server answers with the Markdown twin at the same URL. Browsers still get HTML.

*Same URL, different representation*

```
curl -s -H 'Accept: text/markdown' https://agentnative.build/future
```

## What is deliberately not here?

- **Declarative WebMCP.** The proposal marks the form-based syntax as to be determined, so only the imperative API is used.
- **Authentication.** The content is public and read-only. Write tools would need scoped, per-agent credentials.
- **Server discovery metadata.** Discovery conventions for MCP servers are still moving, so none is published yet.
- **Write tools.** Nothing on this site changes state, so there is nothing to approve, undo, or audit.

## Frequently asked questions

**What is llms-full.txt?** A single Markdown file that contains the full content of a site, so an agent can load everything in one request. It is a community convention that complements the shorter llms.txt index.

**Does this site have an MCP server?** Yes. A read-only remote MCP server runs at https://agentnative.build/api/mcp and exposes five tools: get_definition, list_principles, score_product, get_page, and search_site.

**Does this site support WebMCP?** Yes, when the browser exposes the WebMCP API. The page registers seven tools through navigator.modelContext and registers nothing otherwise.