# gleanyard (read-only) (remote · gleanyard-connector.leima.workers.dev)

Search gleanyard source recipes and read public gleanyard projects' records and health.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `gleanyard-connector.leima.workers.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/kausalflow-gleanyard/gleanyard-connector.md), [page](https://verifymcp.io/servers/kausalflow-gleanyard/gleanyard-connector)

## Channel facts

- Endpoint: `https://gleanyard-connector.leima.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.14.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 560 tokens (~80/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 69% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the gleanyard (read-only) MCP server?

gleanyard (read-only) is a hosted endpoint at https://gleanyard-connector.leima.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http kausalflow-gleanyard 'https://gleanyard-connector.leima.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "kausalflow-gleanyard": {
      "url": "https://gleanyard-connector.leima.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kausalflow-gleanyard": {
      "type": "http",
      "url": "https://gleanyard-connector.leima.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.kausalflow-gleanyard]
url = "https://gleanyard-connector.leima.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kausalflow-gleanyard": {
      "type": "remote",
      "url": "https://gleanyard-connector.leima.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kausalflow-gleanyard --url 'https://gleanyard-connector.leima.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kausalflow-gleanyard:
    url: "https://gleanyard-connector.leima.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "kausalflow-gleanyard": {
      "Transport": "http",
      "Url": "https://gleanyard-connector.leima.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add kausalflow-gleanyard -t streamable-http -u 'https://gleanyard-connector.leima.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "kausalflow-gleanyard": {
      "type": "http",
      "url": "https://gleanyard-connector.leima.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 64)

First indexed and scored.

## MCP tools (7)

### `get_started` (~34 tokens)

How to start a gleanyard project

Explain how to start a gleanyard collection project without installing anything (template repo, Claude Code on the web, Codespaces).

### `search_recipes` (~80 tokens)

Search the source registry

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.

Input parameters:

- `query` (string): Words to match in id, name, description, tags or host.
- `schema` (string): Only recipes for this schema, e.g. family-event.

### `get_recipe` (~46 tokens)

Read one recipe

Read one registry recipe: its index entry, source file, recipe notes and terms evidence, and the command that installs it.

Input parameters:

- `recipe` (string, required): Recipe id from search_recipes.

### `get_schema` (~33 tokens)

Read a registry schema

Read a record schema the registry's recipes are written for, e.g. family-event.

Input parameters:

- `name` (string, required)

### `project_status` (~66 tokens)

Health of a public project

Read status.json of a public gleanyard project on GitHub: each source's health, record count, warnings and last success.

Input parameters:

- `ref` (string): Branch or tag (default: the default branch).
- `repo` (string, required): owner/name of a public GitHub repo.

### `search_records` (~130 tokens)

Search a project's published records

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.

Input parameters:

- `limit` (integer)
- `path` (string): Export file in the repo, if not the default.
- `ref` (string): Branch or tag (default: the default branch).
- `repo` (string, required): owner/name of a public GitHub repo.
- `source_id` (string): Only records from this source.
- `text` (string): Case-insensitive text to find in a record.

### `recent_changes` (~73 tokens)

Recent changes in a project

Records added, changed or removed lately in a public gleanyard project, newest first, from its change feed (exports/changes.json).

Input parameters:

- `limit` (integer)
- `ref` (string)
- `repo` (string, required): owner/name of a public GitHub repo.
- `source_id` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kausalflow-gleanyard/gleanyard-connector#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 70
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 67
- 2026-11-14: 67
- 2026-11-13: 66
- 2026-11-12: 66
- 2026-11-11: 65
- 2026-11-10: 65
- 2026-11-09: 64

## Common questions

### What is the gleanyard (read-only) MCP server?

gleanyard (read-only) is an MCP server listed in the public MCP registry as io.github.kausalflow/gleanyard. Search gleanyard source recipes and read public gleanyard projects' records and health. This page covers its hosted endpoint (https://gleanyard-connector.leima.workers.dev/mcp).

### Is the gleanyard (read-only) MCP server safe to use?

gleanyard (read-only) scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the gleanyard (read-only) MCP server expose?

gleanyard (read-only) exposes 7 tools: get_started, search_recipes, get_recipe, get_schema, project_status, and 2 more. Their descriptions and schemas cost roughly 462 tokens of context every time the server is loaded.

### Does the gleanyard (read-only) MCP server require authentication?

No. We connected to gleanyard (read-only) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the gleanyard (read-only) MCP server still maintained?

gleanyard (read-only) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the gleanyard (read-only) MCP server?

VerifyMCP ran 12 checks on gleanyard (read-only), covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about gleanyard (read-only): HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://gleanyard-connector.leima.workers.dev/mcp
- Repository: https://github.com/kausalflow/gleanyard
- Website: https://kausalflow.github.io/gleanyard/concepts/no-install/
- Changelog RSS feed: https://verifymcp.io/servers/kausalflow-gleanyard/gleanyard-connector.xml
- Changelog JSON feed: https://verifymcp.io/servers/kausalflow-gleanyard/gleanyard-connector/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/kausalflow-gleanyard/gleanyard-connector.json
- HTML version of this page: https://verifymcp.io/servers/kausalflow-gleanyard/gleanyard-connector
