A directory your agent can read.

Start with a question

Find Icelandic weather services that only read information. Show the setup instructions and tell me what has actually been checked.

An agent can fetch the catalogue, match category and actions, and return the source-backed record. The JSON file is a complete snapshot; filters run in your client.

{
  "category": "Weather",
  "actions": "read",
  "connectionTest": null
}

Stable records and clear evidence

• Every service has a stable ID and an individual HTML, JSON and Markdown page.
• lastSourceReview records when documentation was checked. It does not describe software age or uptime.
• connectionTest: null and independentSecurityReview: null mean that no such check is recorded.
• A hosted URL or local package name points to the provider. Reading this directory does not connect you to that service.

Discovery is still a distribution task

Readable pages, a sitemap and structured records give search engines and agents useful entry points. A domain alone does not make every agent aware of the directory. Client integrations and links from relevant providers will also matter.

This first version provides a static JSON feed. It does not yet expose its own MCP server or claim compatibility with the full MCP Registry API. The reading guide is an additional entry point, not a universal discovery standard.