The Chancery Lane Project
Server Details
A connector providing AI assistants searchable access to climate-aligned contract clauses, glossary terms, and practical guides from The Chancery Lane Project's curated knowledge graph.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- The Chancery Lane Project
TDQS
Scored across 6 tools
Most tools have crisp boundaries: search vs entity_lookup is explicitly contrasted (semantic fusion vs deterministic name match), find_legal_resources vs get_legal_resource is list vs fetch-by-id, and taxonomy_facets is clearly the vocabulary-discovery step before taxonomy_content. The one soft spot is that find_legal_resources (filters jurisdiction/sector) and taxonomy_content with scope="legal_resource" can return the same objects, and search vs taxonomy_content overlap on browsing clauses/guides; the descriptions hint at but do not fully rule out this redundancy.
Names are readable but mix conventions: verb_noun in find_legal_resources and get_legal_resource, noun_form in entity_lookup and taxonomy_content, bare verb in search, and a plural/singular pair (find_legal_resources vs get_legal_resource) that is not a clean pattern. The taxonomy_ prefix pairing is the only strong consistency signal.
Six tools for a read-only knowledge-graph lookup server is well-scoped: text search, exact entity lookup, faceted browse, facet discovery, and legal-resource list/detail. Each tool covers a distinct access path and none feels padded or missing a partner.
The surface covers the realistic retrieval lifecycle end to end: discover vocabulary, filter by facet, free-text search, exact concept lookup, then resolve cited instruments to a detail view. It is a read-only domain (no write operations expected), and the cross-tool handoffs (references.work_id to get_legal_resource, taxonomy_facets to taxonomy_content) close the obvious dead ends.
Available Tools
6 toolsentity_lookupARead-onlyInspect
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.
Inputs: name (required), limit, include_full_text. Returns: meta, results
find_legal_resourcesARead-onlyInspect
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`).
Inputs: limit, query, nature, offset, +3 more. Returns: meta, results
get_legal_resourceARead-onlyInspect
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.
Inputs: work_id (required), citing_limit. Returns: meta, citing, resource, citing_total
searchARead-onlyInspect
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.
Inputs: query (required), limit, rerank, node_type, +2 more. Returns: meta, results
taxonomy_contentARead-onlyInspect
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.
Inputs: filters (required), sort, limit, scope, +1 more. Returns: meta, results
taxonomy_facetsARead-onlyInspect
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).
Inputs: scope. Returns: meta, facets
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.MIT
- AlicenseCqualityCmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs112 npm37 PyPIMIT
- AlicenseAqualityDmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.1611 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityCmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.