Read the semantics, not the scripts.
Server-side intake sanitizes public HTML. Forms, repeated content and tables become candidates, while host policies and redirect checks constrain what can be fetched.
Semantic HTML → typed candidates
02 / Agent-native interfacesDesigned & built by Himanshu Jha
Graft
A website becomes a tool. Deliberately.
Turn semantic HTML into reviewed WebMCP tools. Inspect the evidence behind each contract, export an adapter, and check the tools a deployed site exposes.
See the build01 / 04 · Product screenshot
What to look for
The page on the left. Its tools on the right.
Graft compiles the owned Signal Cabinet fixture into seven candidates: five ready, one held and one rejected. The source preview stays beside the contracts it produced.
Browser capture · owned demonstration catalog01 / The problemWhy this
Why this
needed building.
A page can be easy for a person to use and still be a brittle interface for an agent. Generating tool names is easy; deciding what a tool means, whether it is safe, and whether the deployed contract still matches is harder.
I built a workbench that derives typed tool candidates from semantic HTML, shows the evidence behind each candidate, and lets an owner review what gets exported.
02 / Architecture
Follow the system.
The engineering behind the screens, in three stages.
Show why a contract was proposed.
Confidence comes with reasons. Ambiguous candidates are held for review. An owner can repair names and descriptions before a contract ships.
Evidence → review → approved contract
Verify the tools on the real site.
The export bundles reviewed contracts and their runtime. A separate verifier inspects a deployed site and compares registered tool names with the expected set to expose drift.
Adapter → owner site → drift check
03 / DecisionsThe choices
The choices
that matter.
Confidence needs an explanation
An accessible name and a guessed class name are different evidence. The inspector makes that difference visible instead of hiding it behind one score.
Hold uncertain actions
A derived write does not automatically become an executable handler. Review is a real shipping boundary.
Verify across origins
An independently deployed owner example and OmniDev’s Agent Lab exercise the path beyond the workbench itself.
04 / Evidence
Inspect it for yourself.
Interactive workbench, owner-site example and exported adapters.
Scope & limits
Explore the repository Generated contracts are review artifacts, not a blanket guarantee of production safety. The public owner example uses a demonstration catalog. Historical verifier results in the repository describe their recorded runs.
Agent-native design starts with an inspectable contract, and continues after deployment.
Next build / Memory governanceContextFirewall