Search gleanyard source recipes and read public gleanyard projects' records and health.
Scored across 7 tools
The seven tools split cleanly into registry reads (get_recipe, get_schema, search_recipes), project reads (project_status, recent_changes, search_records), and onboarding (get_started), with each targeting a distinct artifact (status.json, changes.json, records.jsonl). The only mild overlap is get_recipe vs get_schema (both 'read one named thing from the registry') and get_recipe vs search_recipes, but the descriptions make the single-vs-search and recipe-vs-schema distinction clear.
Five of seven names follow a clean verb_noun pattern (get_recipe, get_schema, get_started, search_recipes, search_records). Two deviate with verbless forms (project_status, recent_changes), which should arguably be get_project_status / list_recent_changes, but they remain readable and unambiguous.
Seven tools is well within the sweet spot for a focused read-only registry/inspection server. Each tool maps to a concrete artifact or workflow step with no filler or redundant entries.
Core read paths are covered: discover recipes, read a recipe, read a schema, inspect a project's status/changes/records, plus onboarding. However, there is no way to enumerate schemas or projects (get_schema requires knowing the exact schema name, and project tools require knowing the repo), and no tool to read a single record or filter changes by source, leaving real dead ends for discovery.
Read one registry recipe: its index entry, source file, recipe notes and terms evidence, and the command that installs it.
Inputs: recipe (required).
Read a record schema the registry's recipes are written for, e.g. family-event.
Inputs: name (required).
Explain how to start a gleanyard collection project without installing anything (template repo, Claude Code on the web, Codespaces).
Inputs: no named parameters.
Read status.json of a public gleanyard project on GitHub: each source's health, record count, warnings and last success.
Inputs: repo (required), ref.
Records added, changed or removed lately in a public gleanyard project, newest first, from its change feed (exports/changes.json).
Inputs: repo (required), ref, limit, source_id.
Search the public gleanyard source registry for recipes: sources that already work, with a fixture, a terms review and a health count. Empty query lists all.
Inputs: query, schema.
Search the rights-filtered export of a public gleanyard project (exports/records.jsonl, or the path its dataherb.json names) by text, optionally for one source.
Inputs: repo (required), ref, path, text, +2 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Search and compare attributed recipe records through a public read-only remote MCP endpoint.
Search structured recipes, scale servings, match pantry ingredients, and build shopping lists.
Search, read, and write highlights, notes, screenshots, collections, projects, and tags in Gleanit.
Add one secure layer between your agents and this server.
