io.github.thechancerylaneproject/tclp-mcp
REMOTE · MCP.CHANCERYLANEPROJECT.ORG · SCANNED SEP 22
MCP server for The Chancery Lane Project's climate-aligned contract clause knowledge graph.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1052 tokens (~263/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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'
{
"mcpServers": {
"thechancerylaneproject-tclp-mcp": {
"url": "https://mcp.chancerylaneproject.org/mcp"
}
}
} {
"servers": {
"thechancerylaneproject-tclp-mcp": {
"type": "http",
"url": "https://mcp.chancerylaneproject.org/mcp"
}
}
} [mcp_servers.thechancerylaneproject-tclp-mcp] url = "https://mcp.chancerylaneproject.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"thechancerylaneproject-tclp-mcp": {
"type": "remote",
"url": "https://mcp.chancerylaneproject.org/mcp",
"enabled": true
}
}
} openclaw mcp add thechancerylaneproject-tclp-mcp --url 'https://mcp.chancerylaneproject.org/mcp' --transport streamable-http
mcp_servers:
thechancerylaneproject-tclp-mcp:
url: "https://mcp.chancerylaneproject.org/mcp" {
"McpServers": {
"thechancerylaneproject-tclp-mcp": {
"Transport": "http",
"Url": "https://mcp.chancerylaneproject.org/mcp"
}
}
} assistant mcp add thechancerylaneproject-tclp-mcp -t streamable-http -u 'https://mcp.chancerylaneproject.org/mcp'
{
"mcpServers": {
"thechancerylaneproject-tclp-mcp": {
"type": "http",
"url": "https://mcp.chancerylaneproject.org/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 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.
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 22 Sept 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 | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | a89a363268bc4a9e0e8f60cbce636735 |
| 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. | present | 26974 | 8 | Verified |
| chancerylaneproject.org. | absent | 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 ~231
Find TCLP content nodes (clauses, glossary terms) 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 and the entity names that matched.
| 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.
search ~237
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), "lrsf" (laws, regulations, standards, frameworks), or "all". 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, and optionally relationships and full_text).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 ~271
List TCLP content (clauses, guides) 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`, `guide`, or `all` (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, and a `facets` map of all taxonomy arrays on the node).
| 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 ~186
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), or `all` (both, 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.
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 4 tools: search, entity_lookup, taxonomy_facets, taxonomy_content. Their descriptions and schemas cost roughly 925 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 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.