Engelberg Center Corpus MCP server
org.nyuengelberg/corpusnyuengelberg.orgstreamable-httpv1.0.2Scanned
IP and innovation law scholarship of NYU's Engelberg Center, with verified Bluebook pin cites.
4 tools: 4 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Engelberg Center Corpus MCP server can do
The Engelberg Center Corpus MCP server is published by nyuengelberg.org, a domain the MCP Registry verified. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
2 tools read private data (fetch_document and list_documents).
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.0.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
fetchRetrieve the full text of an Engelberg Center publication by the id returned from search.No findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
Description, as the server wrote it Retrieve the full text of an Engelberg Center publication by the id returned from search. Returns id, title, text, url, and metadata (citation, version, and how to cite — including that author-draft page numbers must never be presented as journal pin cites; see metadata.citation_note). Very long documents (casebooks) are truncated; metadata.truncated is true and fetch_document(document_id, start_chunk=...) pages through the remainder. Args: id: The document id from a search result
fetch_documentRetrieve the text of a specific Engelberg Center publication by document ID.Reads private dataNo findings
Why it is in this group
- The name "fetch_document" says "fetch": a word for reading.
What it can reach
- private-dataThe name "fetch_document" says "fetch" and "document": it reads documents.
- private-dataThe description's first sentence says "retrieve" and "document": it reads documents.
Description, as the server wrote it Retrieve the text of a specific Engelberg Center publication by document ID. Use after a search() call to get more context around a relevant chunk, or to read a paper in page order. Long documents are paged: at most max_chunks chunks are returned per call, starting at start_chunk. The response includes total_chunks and next_start_chunk (null when you have reached the end) — pass next_start_chunk back to continue reading. Returns document metadata (including version: "published" or "author_draft" — see citation_note for how to cite drafts) and text chunks in sequence with page numbers and section headings. Args: document_id: The document ID returned by search() or list_documents() start_chunk: Zero-based chunk offset to start from (default 0) max_chunks: Maximum chunks to return (default 40, max 100)
list_documentsList publications from the Engelberg Center on Innovation Law & Policy at NYU Law.Reads private dataNo findings
Why it is in this group
- The name "list_documents" says "list": a word for reading.
What it can reach
- private-dataThe name "list_documents" says "list" and "document": it reads documents.
Description, as the server wrote it List publications from the Engelberg Center on Innovation Law & Policy at NYU Law. Filter by author name, publication type, or cited case. Publication types: Articles, Books, Chapters, Short Articles, Briefs & Testimony (amicus briefs, regulatory comment letters, and congressional testimony), Reports (clinic white papers, policy reports, guides, and explainers), Transcripts (machine-generated transcripts of Engelberg Center Live! podcast episodes and event recordings; the director filter matches their labeled speakers), Working Papers (never journal-published; the working paper is citable) Directors include the eight Engelberg Center co-directors and affiliated co-authors. Use this — not search — to answer what the corpus contains or holds. Use to browse available sources before searching, to find all work by a specific author, or to find which publications discuss a specific judicial decision (cites_case) — e.g. cites_case="MercExchange" or cites_case="547 U.S. 388". Results matched on a case include cited_case_matches showing how often each matched case is cited — higher counts mean the case is analyzed, not just cited in passing. Args: director: Filter by author name (partial match, case-insensitive) publication_type: Filter by type — Articles, Books, Chapters, Short Articles cites_case: Filter to publications citing a case; matches on party names or the reporter citation (partial, case-insensitive)
searchSearch the published research corpus of the Engelberg Center on Innovation Law & Policy at NYU Law: the scholarship of Barton Beebe, Rochelle C.1 finding
Why it is in this group
- The name "search" says "search": a word for reading.
Findings
- Info
The description is 3,200 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...can continue their exploration. Args: query: Natural language search query"
Description, as the server wrote it Search the published research corpus of the Engelberg Center on Innovation Law & Policy at NYU Law: the scholarship of Barton Beebe, Rochelle C. Dreyfuss, Jeanne C. Fromer, C. Scott Hemphill, Christopher J. Morten, Jason M. Schultz, Christopher Jon Sprigman, Katherine J. Strandburg, Michael Weinberg, the Center's research collaborators (including Kate Crawford, Mike Ananny, Melodi Dincer, and Jake Karr), and their co-authors — roughly 350 works covering intellectual property law (patent, trademark, copyright, trade secrets), innovation policy, technology law, fashion law, data governance, AI training datasets and the law of generative AI, and competition/antitrust as they intersect with IP and innovation — plus transcripts of the Center's podcast and event recordings (Engelberg Center Live!, 2019–present: panels, keynotes, book talks, and the Knowing Machines podcast). ALWAYS search this corpus when a question names one of these authors or involves IP law doctrine, innovation economics, AI datasets, or technology policy and you want authoritative academic sources with verifiable citations. Use it alongside web search rather than instead of it: this corpus returns exact quotable passages with verified, page-accurate Bluebook citations that web search cannot provide, while web search covers the wider literature this collection does not hold. To find which publications discuss a specific judicial decision, use list_documents(cites_case=...) instead — it matches the corpus's extracted tables of authorities. To answer what the corpus contains (which works, authors, or publication types it holds), call list_documents instead — this tool searches passage text, not the catalog. Returns ranked text chunks with full citation metadata. Each result has: - bluebook_citation: the exact Bluebook citation for the passage, pin cite included where the printed page is known. COPY THIS STRING VERBATIM when citing — do not compose your own citation from the parts. - citation: the published citation of the work - version: "published" (version of record) or "author_draft" (an SSRN / working-paper copy). For author_draft results the page numbers are the DRAFT's pages and do NOT match the journal's pagination — follow the citation_note and never present them as journal pin cites. - locator: the page to cite. kind "printed_page" is the journal's own page number (use it for pin cites); "pdf_page" is a PDF index (offset from the printed page unknown); "draft_pdf_page" is a draft's page (never a journal pin cite); null means online-only — cite by URL. - Transcript results (publication_type "Transcripts", at most 2 per search) are machine-generated event/podcast transcripts, not publications: speaker names who said the passage (attribute quotes to them), timestamp/locator kind "timestamp" gives the position in the audio, and bluebook_citation carries it as "at 12:34". - url: the work's canonical home (publisher page, SSRN, etc.). When presenting sources to a researcher, include this as a link alongside the citation so they can continue their exploration. Args: query: Natural language search query
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:17 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
- Infosearch
The description is 3,200 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...can continue their exploration. Args: query: Natural language search query"
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:list_documentsOnly readsdescription
- Changed:searchOnly readsdescription
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http corpus https://corpus.nyuengelberg.org/mcpclaude mcp add --transport http corpus https://corpus.nyuengelberg.org/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__corpus__search",
"mcp__corpus__fetch",
"mcp__corpus__fetch_document",
"mcp__corpus__list_documents"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as corpus. Review it before you use it.
Capability tags behind 2 rules
- mcp__corpus__fetch_document private-data
- mcp__corpus__list_documents private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/org.nyuengelberg/corpus/verify?hash=1f4bf8e586577f35e312a76de2906e162e88517a5286a500bbb68fb237b650b3" | jq -e '.changed == false'Pinned hash 1f4bf8e58657, from Nov 20, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/org.nyuengelberg/corpus/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/org.nyuengelberg/corpus)Source: MCP Registry. Synced Nov 20, 2026, 07:18 UTC.
Engelberg Center Corpus MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Engelberg Center Corpus MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 1 finding from fixed checks. Read-only tools can still pass private data to a model.
Can the Engelberg Center Corpus MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Engelberg Center Corpus MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Engelberg Center Corpus MCP server have?
- 4 tools: 4 read. search, fetch, fetch_document and list_documents.
Does the Engelberg Center Corpus MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Engelberg Center Corpus MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Engelberg Center Corpus MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.