Connect your agent

The feed

https://shelf.scotf.org/manifest.json

One JSON document, rebuilt with the site. It lists published resources and the open-source resources the initiative points to. No key, no sign-up, no rate limit.

The feed is described by a published schema: manifest.schema.json (JSON Schema 2020-12). The build fails if the feed does not match it, so an agent that trusts the schema will not be surprised by a release.

What each entry tells you

slug, title, subtitle, summary

What the resource is, in one or two sentences.

type, typeLabel, workstream

Which kind of resource it is and which part of the initiative produced it.

license, licenseName

The license for that resource. Licenses differ across the Shelf; read this per item rather than assuming one license for everything.

version, status, published

How finished it is. A v0.9 item is an early draft, published to be improved.

company, contributors

Who contributed it. A company is named only with its approval.

url, pdf

The readable page and the PDF.

tags

Topics, for matching against a question.

From a shell

# Everything on the Shelf, with licenses
curl -s https://shelf.scotf.org/manifest.json | jq '.items[] | {title, license, url}'

# Only what you may use commercially
curl -s https://shelf.scotf.org/manifest.json | jq '.items[] | select(.license == "CC-BY-4.0")'

From an assistant

The Shelf is a static site, so any assistant that can fetch a URL can read it. There is no bespoke server to install. If your client uses the Model Context Protocol, allow this host with a fetch server and the whole Shelf becomes available to it:

{
  "mcpServers": {
    "the-shelf": {
      "command": "npx",
      "args": ["-y", "mcp-server-fetch"],
      "env": { "FETCH_ALLOWLIST": "https://shelf.scotf.org" }
    }
  }
}

Paste this into your client's MCP configuration file. Adjust the server name to whichever fetch server your client already trusts.

What to ask for

Three things worth getting right when an agent uses this material:

• Quote the license. It differs per resource and it is in every entry. Nothing here is licensed in bulk.
• Quote the version and status. A v0.9 draft should not be cited as a settled industry position.
• Carry the credit. Each entry names its contributors; a listing is not an endorsement of any company, product or tool.