Developing

lnk-link-web is Link Web: an MCP server over stdio with two calls, fetch and search, for any harness to reach as a tool. How to use it, and why it works the way it does: Link Web.

What it reads of a harness

It reads one thing of a harness's. A call's _meta may hold "link.local/spec", the agent's spec's table for the tool, and its fetch sets the part's size. Link Harness sends it, and without it a part is 24 KB.

Build and test

From tools/, in the public workspace beside the core (LINK_CORE for a core in another place):

cargo build -p link-plugin-link-web
cargo test -p link-plugin-link-web

Its tests

web/tests/mcp.rs drives it over stdio against pages and search APIs served on this machine, named with --private-host 127.0.0.1, and reaches the search API at LNK_WEB_SEARCH_URL. No test reaches the internet or spends a search.

The pinned-address fixture

The pinned-address unit fixture runs in a child without inherited proxy variables, so its synthetic hostname is resolved by the client's pinned resolver. Other tests keep their environment; the fixture never changes process-wide variables while tests run concurrently.