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.

Cedwyn archive (read-only)

REMOTE · CEDWYN.BUCKLERFAMILY.ESTATE

Read-only archive of Tŷ Mawr (Great House Farm), Llandough, Wales: names, e-books, pages, hashes.

+3 this week 72 Trust /100

Last scanned (13 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • 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 Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 428 tokens (~61/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 Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% 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 (13)

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

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 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 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.

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 9 Nov 26 +1

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

  • 7 Nov 26 +1

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

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://cedwyn.bucklerfamily.estate/mcp/archive

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cedwyn.bucklerfamily.estate CN=WE1,O=Google Trust Services,C=US 24 Oct 2026 22 Jan 2027 ECDSA 256 ECDSA-SHA256 2369e21d5722d72d0e7da057caa4e502
SANs: cedwyn.bucklerfamily.estate
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 cedwyn.bucklerfamily.estate. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
estate. DS published 9302 8 Verified
bucklerfamily.estate. 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://cedwyn.bucklerfamily.estate/mcp/archive Verified 200
http (plaintext) http://cedwyn.bucklerfamily.estate/mcp/archive Served over HTTP 200
MCP tools · 7 exposed · ~359 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_catalogue_export ~40

Return the open-data export of the central evidence database: tables, row counts, columns and the download path and SHA-256 of every CSV file.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_cedwyn_guide ~40

Return the site's llms.txt: what the archive is, how outside records are treated, and where every section lives. Read this first.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_provenance ~54

Return the SHA-256 list of the published catalogue export and discovery files, anchored with OpenTimestamps on 5 Nov 2026, and how to verify a file yourself.

NameTypeReqDescription
path_containsstring––

No output schema declared.

No examples provided.

list_cedwyn_ebooks ~38

List the e-books published at /ebooks/ with their titles and page paths (free and paid editions are explained on each page).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_open_agent_jobs ~29

Return the Cedwyn Academy work board: open, claimable research jobs with definitions of done.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_cedwyn_page ~72

Fetch one public page of cedwyn.bucklerfamily.estate by path (e.g. /ebooks/enwau/ or /values/) and return its title, headings, plain text (max 20,000 characters) and same-site links.

NameTypeReqDescription
pathstringyesSite path starting with /

No output schema declared.

No examples provided.

search_cedwyn_names ~86

Search the published nomenclature register (Tŷ Mawr, Great House Farm, Cedfin/Cedwyn and every recorded spelling). Returns the concept, variant, first record year, catalogue source id and page path. Matches are retrieval aids, not proof that two places are identical.

NameTypeReqDescription
limitinteger––
qstringyesName, spelling or place

No output schema declared.

No examples provided.

Install

How do I install the Cedwyn archive (read-only) MCP server?

Cedwyn archive (read-only) is a hosted endpoint at https://cedwyn.bucklerfamily.estate/mcp/archive, 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 · cedwyn.bucklerfamily.estate

# add to Claude Code
claude mcp add --transport http estate-bucklerfamily-cedwyn-archive 'https://cedwyn.bucklerfamily.estate/mcp/archive'
Common questions

What is the Cedwyn archive (read-only) MCP server?

Cedwyn archive (read-only) is an MCP server listed in the public MCP registry as estate.bucklerfamily.cedwyn/archive. Read-only archive of Tŷ Mawr (Great House Farm), Llandough, Wales: names, e-books, pages, hashes. This page covers its hosted endpoint (https://cedwyn.bucklerfamily.estate/mcp/archive).

Is the Cedwyn archive (read-only) MCP server safe to use?

Cedwyn archive (read-only) scores 72 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 Cedwyn archive (read-only) MCP server expose?

Cedwyn archive (read-only) exposes 7 tools: get_cedwyn_guide, search_cedwyn_names, list_cedwyn_ebooks, read_cedwyn_page, get_catalogue_export, and 2 more. Their descriptions and schemas cost roughly 359 tokens of context every time the server is loaded.

Does the Cedwyn archive (read-only) MCP server require authentication?

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

Is the Cedwyn archive (read-only) MCP server still maintained?

Cedwyn archive (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 Cedwyn archive (read-only) MCP server?

VerifyMCP ran 13 checks on Cedwyn archive (read-only), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.