io.github.thechancerylaneproject/tclp-mcp
REMOTE · MCP.CHANCERYLANEPROJECT.ORG
MCP server for The Chancery Lane Project's climate-aligned contract clause knowledge graph.
Available components
Last scanned (15 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
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 Security74
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2416 tokens (~402/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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 →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Oct 26 0
- Tool “search” rewrote its description, which is the text the model reads security
- Tool “entity_lookup” rewrote its description, which is the text the model reads security
- Tool “taxonomy_content” rewrote its description, which is the text the model reads security
- Server version: 1.2.2 → 1.3.0 functional
- “search” added an optional parameter “content_type” cosmetic
- 10 Oct 26 0
- Tool “entity_lookup” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Server version: 1.2.1 → 1.2.2 functional
- 2 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “entity_lookup” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Tool “taxonomy_content” rewrote its description, which is the text the model reads security
- Tool “taxonomy_facets” rewrote its description, which is the text the model reads security
- Schema quality: 263 → 358 ▼ functional
- Schema quality: good → excellent functional
- Server version: 1.27.2 → 1.1.0 functional
- New tool “find_legal_resources” functional
- New tool “get_legal_resource” functional
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://mcp.chancerylaneproject.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chancerylaneproject.org | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2fde164efe273c290eb7ca9cf5dca792 |
| SANs: chancerylaneproject.org, *.chancerylaneproject.org | ||||||
| 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 mcp.chancerylaneproject.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| org. | DS published | 725 | 8 | Verified |
| chancerylaneproject.org. | 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://mcp.chancerylaneproject.org/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.chancerylaneproject.org/mcp | HTTPS enforced | 301 | https://mcp.chancerylaneproject.org/mcp |
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 →
entity_lookup ~378
Find TCLP content (clauses, glossary terms, guides) associated with a named concept. Unlike `search`, this performs a deterministic name match against Entity nodes in the knowledge graph rather than a relevance-ranked semantic search. Use it when you have a specific term or concept (e.g. "scope 3 emissions", "net zero") and want to retrieve every clause or glossary entry that explicitly references it. Args: name: The entity or concept name to look up (exact match, case-insensitive). limit: Maximum number of results to return (1–50). include_full_text: Include each hit's full body text (Markdown). Off by default — bodies are large; request only when you need the content, and prefer a small `limit` when you do. Returns: JSON with "meta" and "results" where each hit includes the source content node, its plain-text `summary` (null when it has none), its `child_name` (a clause's child name, null otherwise) and the entity names that matched. Each hit's "references" lists the instruments it cites: pass a reference's `work_id` to `get_legal_resource` for details. A reference's `edge` (governs, references, describes) says how the content relates to the instrument; it is not a statement of the instrument's legal effect. An empty list means the hit cites no instruments. null with "lrsf" in meta.degraded means references could not be loaded: do not conclude that the hit cites no instruments.
| Name | Type | Req | Description |
|---|---|---|---|
| include_full_text | boolean | – | – |
| limit | integer | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | – | yes | – |
| results | array | yes | – |
No examples provided.
find_legal_resources ~489
Find the laws, regulations, standards, frameworks and guidance that TCLP content refers to. This is not a general legal database: it holds only the instruments that TCLP clauses, guides and glossary terms cite. Status "stub": identity confirmed, metadata minimal; a null or empty field means not yet recorded, not that it does not apply. On a stub, `nature` may be an unreviewed inference, and is often null. Do not fill in missing fields from your own knowledge, and do not state an instrument's legal effect. A filter on nature, sector or bindingness excludes works where that field is not recorded. Most works do not record these yet, so an empty result does not mean that TCLP content cites no such instrument; prefer `query` or `jurisdiction`. Args: query: Case-insensitive substring match on name and aliases (e.g. "CSRD"), at most 200 characters. An exact name or alias match ranks first. nature: Any of "legislation", "regulation", "standard", "framework", "guidance". jurisdiction: Jurisdiction slugs, matched exactly: lower-case letters, digits and hyphens (e.g. "european-union"). Get valid values from `taxonomy_facets(scope="legal_resource")`. sector: Sector slugs, matched exactly: lower-case letters, digits and hyphens. Get valid values from `taxonomy_facets(scope="legal_resource")`. bindingness: Any of "binding", "comply_or_explain", "voluntary", "depends". Each list filter takes at most 20 values. limit: Maximum results (1–100, default 20). offset: Result offset for paging (0–10000, default 0). Returns: JSON with "meta" (total_available, limit, offset) and "results" (one entry per instrument, with `work_id` for `get_legal_resource` and `citing_count`).
| Name | Type | Req | Description |
|---|---|---|---|
| bindingness | – | – | – |
| jurisdiction | – | – | – |
| limit | integer | – | – |
| nature | – | – | – |
| offset | integer | – | – |
| query | – | – | – |
| sector | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | – | yes | – |
| results | array | yes | – |
No examples provided.
get_legal_resource ~246
Get one law, regulation, standard, framework or guidance, and the TCLP content citing it. Versions are not tracked yet, so every citation has `staleness: "unpinned"`: the content cites the instrument without naming a version. There is no description yet; do not supply one from your own knowledge, and do not state the instrument's legal effect. Args: work_id: The instrument's `work_id`, from `find_legal_resources` or from a search result's "references". citing_limit: Maximum citing content items to return (1–100, default 20). Returns: JSON with "resource", "citing" (each with id, title, url, content_type, edge, staleness and child_name: a clause's child name, null otherwise) and "citing_total". `edge` (governs, references, describes) says how the content relates to the instrument; it is not a statement of the instrument's legal effect.
| Name | Type | Req | Description |
|---|---|---|---|
| citing_limit | integer | – | – |
| work_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| citing | array | yes | – |
| citing_total | integer | yes | – |
| meta | – | yes | – |
| resource | – | yes | – |
No examples provided.
search ~484
Search the TCLP knowledge graph using fusion search (semantic + BM25). Args: query: Free-text search query (max 1000 characters). node_type: Content scope — "tclp" (clauses, glossary terms, guides) or "all". Laws, regulations, standards and frameworks are not searchable here: use `find_legal_resources`. content_type: Return only one content type: "clause", "glossary_term" or "guide". Omit to search every type. limit: Maximum number of results to return (1–50). rerank: Whether to apply RRF reranking when combining graph and text results. include_full_text: Include each hit's full body text (Markdown). Off by default — bodies are large; request only when you need the content, and prefer a small `limit` when you do. Returns: JSON with "meta" (totals, timing) and "results" (ranked hits with title, url, content_type, scores, summary, optionally relationships_text, related and full_text). `summary` is short plain text: the clause summary, the first paragraph of a glossary definition, or a guide's excerpt. It is null when the item has none. `child_name` is a clause's child name (e.g. "Odhran's Clause"), null for other content and for a clause that has none; text search also matches it. Each hit's "references" lists the instruments it cites: pass a reference's `work_id` to `get_legal_resource` for details. A reference's `edge` (governs, references, describes) says how the content relates to the instrument; it is not a statement of the instrument's legal effect. An empty list means the hit cites no instruments. null with "lrsf" in meta.degraded means references could not be loaded: do not conclude that the hit cites no instruments.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | – | – | – |
| include_full_text | boolean | – | – |
| limit | integer | – | – |
| node_type | string | – | – |
| query | string | yes | – |
| rerank | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | – | yes | – |
| results | array | yes | – |
No examples provided.
taxonomy_content ~391
List TCLP content (clauses, guides) or legal resources filtered by taxonomy facet=value. Multi-facet filters are combined with AND. Call `taxonomy_facets` first to learn which facet names and slugs exist; using a name not in that list returns a 400. Args: filters: Mapping of facet name to value slug, e.g. `{"sector": "real-estate", "practice_area": "commercial"}`. Each facet may appear at most once. scope: `clause` (ClauseName only), `guide` (Guide only), `legal_resource` (laws, regulations, standards and frameworks; facets `jurisdiction` and `sector` only), or `all` (clauses and guides, the default). limit: Maximum results to return (1–100, default 25). offset: Result offset for paging (default 0). sort: `title`, `date_published_desc`, or `date_modified_desc`. Returns: JSON with "meta" (totals, scope, filters echoed back) and "results" (each hit has `id`, `url`, `title`, `content_type`, dates, `summary` (the clause summary or guide excerpt as plain text, null for legal resources), `child_name` (a clause's child name, e.g. "Odhran's Clause", null otherwise), and a `facets` map of all taxonomy arrays on the node). `content_type` is `clause`, `guide` or `legal_resource`, the same values that `search` returns.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
| scope | string | – | – |
| sort | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | – | yes | – |
| results | array | yes | – |
No examples provided.
taxonomy_facets ~216
List taxonomy facets and their value slugs across TCLP content. Facets are taxonomy categories like `sector`, `practice_area`, `application`, and `jurisdiction`. Each facet returns the list of slugs that actually appear on the graph, with counts. Use this to discover the vocabulary, then call `taxonomy_content` with chosen slugs. Args: scope: Which labels to include — `clause` (ClauseName only), `guide` (Guide only), `legal_resource` (laws, regulations, standards and frameworks; facets `jurisdiction` and `sector` only), or `all` (clauses and guides, the default). Returns: JSON with "meta" and "facets". Each facet has `name`, `applies_to` (list of Neo4j labels carrying it), and `values` (list of `{slug, count}`, sorted by count desc).
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| facets | array | yes | – |
| meta | – | yes | – |
No examples provided.
How do I install the io.github.thechancerylaneproject/tclp-mcp server?
io.github.thechancerylaneproject/tclp-mcp is a hosted endpoint at https://mcp.chancerylaneproject.org/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 · mcp.chancerylaneproject.org
claude mcp add --transport http thechancerylaneproject-tclp-mcp 'https://mcp.chancerylaneproject.org/mcp'
What is the io.github.thechancerylaneproject/tclp-mcp server?
io.github.thechancerylaneproject/tclp-mcp is listed in the public MCP registry as io.github.thechancerylaneproject/tclp-mcp. MCP server for The Chancery Lane Project's climate-aligned contract clause knowledge graph. This page covers its hosted endpoint (https://mcp.chancerylaneproject.org/mcp).
Is the io.github.thechancerylaneproject/tclp-mcp server safe to use?
io.github.thechancerylaneproject/tclp-mcp scores 80 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 io.github.thechancerylaneproject/tclp-mcp server expose?
io.github.thechancerylaneproject/tclp-mcp exposes 6 tools: search, entity_lookup, find_legal_resources, get_legal_resource, taxonomy_facets, taxonomy_content. Their descriptions and schemas cost roughly 2,204 tokens of context every time the server is loaded.
Does the io.github.thechancerylaneproject/tclp-mcp server require authentication?
No. We connected to io.github.thechancerylaneproject/tclp-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.thechancerylaneproject/tclp-mcp server still maintained?
io.github.thechancerylaneproject/tclp-mcp 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 io.github.thechancerylaneproject/tclp-mcp server?
VerifyMCP ran 13 checks on io.github.thechancerylaneproject/tclp-mcp, 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.