The Site That Answers Back
I made this site queryable by AI agents. Instead of scraping the HTML, any agent can ask it directly: my writing, projects, and benchmark results.
Most websites are built for people to read. You land, you skim, you leave. If a machine wants to know what is here, it scrapes the HTML and guesses. I wanted mine to do something better: answer directly.
A second front door, for agents
This site now has an agent-native layer. Any AI agent can connect to it over the Model Context Protocol and ask real questions: search my writing, pull a document, read my profile, get the OPERANT calibration results. No scraping, no guessing. The same words you read, handed to a machine as structured answers.
It is a small, deliberate thing. Read-only. Stateless. No login, no tracking, no database. The whole corpus is baked into the server at build time, so it makes zero network calls while it runs, and none of its tools take a URL or a file path. There is nothing for an agent to wander into. That was the point.
A sibling, not a backend
The website stays a plain static site. The MCP server sits beside it, not bolted underneath it. The site's build emits a machine-readable copy of its own content, the server bakes that copy in, and serves it over six small tools. There is a hosted version on a custom domain, and a local one you can run with a single npx command.
Why verification is the whole point
The throughline here is the same one that runs through everything else in this workshop: verification. An agent is only as trustworthy as the surface you hand it. So the server passes my own auditor cleanly, its discovery manifest is cryptographically signed, and it is listed in the public registries, so the claims are checkable, not just asserted.
There is a small joke buried in this. The note you are reading is part of the corpus the server serves. Ask an agent what I have written about making my site agent-readable, and it can find this. The site documents itself, then answers for itself.
To point an agent at it, the endpoint and the package are linked from the portfolio-mcp project on the home page.