Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

gleanyard (read-only)

REMOTE · GLEANYARD-CONNECTOR.LEIMA.WORKERS.DEV

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

+3 this week 70 Trust /100

Last scanned (13 hours ago)

Scores higher than 55% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Web Scraping

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 560 tokens (~80/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 69% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 10 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://gleanyard-connector.leima.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=leima.workers.dev CN=WE1,O=Google Trust Services,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 6e7d5b527d60885b13d15e4149863eb7
SANs: leima.workers.dev, *.leima.workers.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of gleanyard-connector.leima.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gleanyard-connector.leima.workers.dev/mcp Verified 200
http (plaintext) http://gleanyard-connector.leima.workers.dev/mcp Inconclusive 405
MCP tools · 7 exposed · ~462 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_recipe ~46

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

NameTypeReqDescription
recipestringyesRecipe id from search_recipes.

No output schema declared.

No examples provided.

get_schema ~33

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

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

get_started ~34

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

project_status ~66

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

NameTypeReqDescription
refstring–Branch or tag (default: the default branch).
repostringyesowner/name of a public GitHub repo.

No output schema declared.

No examples provided.

recent_changes ~73

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

NameTypeReqDescription
limitinteger––
refstring––
repostringyesowner/name of a public GitHub repo.
source_idstring––

No output schema declared.

No examples provided.

search_recipes ~80

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.

NameTypeReqDescription
querystring–Words to match in id, name, description, tags or host.
schemastring–Only recipes for this schema, e.g. family-event.

No output schema declared.

No examples provided.

search_records ~130

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.

NameTypeReqDescription
limitinteger––
pathstring–Export file in the repo, if not the default.
refstring–Branch or tag (default: the default branch).
repostringyesowner/name of a public GitHub repo.
source_idstring–Only records from this source.
textstring–Case-insensitive text to find in a record.

No output schema declared.

No examples provided.

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.

remote · gleanyard-connector.leima.workers.dev

# add to Claude Code
claude mcp add --transport http kausalflow-gleanyard 'https://gleanyard-connector.leima.workers.dev/mcp'
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.