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.

org.nyuengelberg/corpus

REMOTE · CORPUS.NYUENGELBERG.ORG · SCANNED SEP 28

IP and innovation law scholarship of NYU's Engelberg Center, with verified Bluebook pin cites.

+4 this week 68 Trust /100
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
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1382 tokens (~345/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 Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 current MCP spec version (2026-07-28).Pass
Install

How do I install the org.nyuengelberg/corpus MCP server?

org.nyuengelberg/corpus is a hosted endpoint at https://corpus.nyuengelberg.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 · corpus.nyuengelberg.org

# add to Claude Code
claude mcp add --transport http org-nyuengelberg-corpus 'https://corpus.nyuengelberg.org/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "org-nyuengelberg-corpus": {
      "url": "https://corpus.nyuengelberg.org/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "org-nyuengelberg-corpus": {
      "type": "http",
      "url": "https://corpus.nyuengelberg.org/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.org-nyuengelberg-corpus]
url = "https://corpus.nyuengelberg.org/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-nyuengelberg-corpus": {
      "type": "remote",
      "url": "https://corpus.nyuengelberg.org/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add org-nyuengelberg-corpus --url 'https://corpus.nyuengelberg.org/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  org-nyuengelberg-corpus:
    url: "https://corpus.nyuengelberg.org/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "org-nyuengelberg-corpus": {
      "Transport": "http",
      "Url": "https://corpus.nyuengelberg.org/mcp"
    }
  }
}
# add to Vellum
assistant mcp add org-nyuengelberg-corpus -t streamable-http -u 'https://corpus.nyuengelberg.org/mcp'
// mcp.json
{
  "mcpServers": {
    "org-nyuengelberg-corpus": {
      "type": "http",
      "url": "https://corpus.nyuengelberg.org/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 28 Sept 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
  • 26 Sept 26 +1

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

  • 25 Sept 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
  • 24 Sept 26 +1

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

  • 22 Sept 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.

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 15 Sept 26 +1
    • Stability: unverified → 0.03 ▲ 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 28 Sept 2026 · Probed https://corpus.nyuengelberg.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=corpus.nyuengelberg.org CN=YE2,O=Let's Encrypt,C=US 1 Sept 2026 30 Nov 2026 ECDSA 256 ECDSA-SHA384 6608c38733f297e2ebc931fbabe86845b95
SANs: corpus.nyuengelberg.org
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of corpus.nyuengelberg.org. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 26974 8 Verified
nyuengelberg.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
Header Value
strict-transport-security max-age=31536000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://corpus.nyuengelberg.org/mcp Verified 200
http (plaintext) http://corpus.nyuengelberg.org/mcp HTTPS enforced 308 https://corpus.nyuengelberg.org/mcp
MCP tools · 4 exposed · ~1,155 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
fetch ~125

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

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
idstringyes–
metadataobjectyes–
text–yes–
title–yes–
url–yes–

No examples provided.

fetch_document ~215

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)

NameTypeReqDescription
document_idstringyes–
max_chunksinteger––
start_chunkinteger––
NameTypeReqDescription
chunksarrayyes–
document–yes–
errorstring––
next_start_chunk–yes–
returnedobjectyes–
total_chunksintegeryes–

No examples provided.

list_documents ~275

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 and congressional testimony by the co-directors), Reports (clinic white papers and policy reports) Directors include the eight Engelberg Center co-directors and affiliated co-authors. 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)

NameTypeReqDescription
cites_casestring––
directorstring––
publication_typestring––
NameTypeReqDescription
countintegeryes–
documentsarrayyes–

No examples provided.

search ~540

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, and their co-authors — roughly 300 works covering intellectual property law (patent, trademark, copyright, trade secrets), innovation policy, technology law, fashion law, data governance, and competition/antitrust as they intersect with IP and innovation. ALWAYS search this corpus when a question names one of these authors or involves IP law doctrine, innovation economics, 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. 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);…

NameTypeReqDescription
querystringyes–
NameTypeReqDescription
querystringyes–
resultsarrayyes–

No examples provided.

Common questions

What is the org.nyuengelberg/corpus MCP server?

org.nyuengelberg/corpus is an MCP server listed in the public MCP registry as org.nyuengelberg/corpus. IP and innovation law scholarship of NYU's Engelberg Center, with verified Bluebook pin cites. This page covers its hosted endpoint (https://corpus.nyuengelberg.org/mcp).

Is the org.nyuengelberg/corpus MCP server safe to use?

org.nyuengelberg/corpus scores 68 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 org.nyuengelberg/corpus MCP server expose?

org.nyuengelberg/corpus exposes 4 tools: search, fetch, fetch_document, list_documents. Their descriptions and schemas cost roughly 1,155 tokens of context every time the server is loaded.

Does the org.nyuengelberg/corpus MCP server require authentication?

No. We connected to org.nyuengelberg/corpus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the org.nyuengelberg/corpus MCP server still maintained?

org.nyuengelberg/corpus is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.