# org.nyuengelberg/corpus (remote · corpus.nyuengelberg.org)

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

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `corpus.nyuengelberg.org`: 68/100 (this document), [markdown](https://verifymcp.io/servers/org-nyuengelberg-corpus/corpus.md), [page](https://verifymcp.io/servers/org-nyuengelberg-corpus/corpus)

## Channel facts

- Endpoint: `https://corpus.nyuengelberg.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http org-nyuengelberg-corpus 'https://corpus.nyuengelberg.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-nyuengelberg-corpus": {
      "url": "https://corpus.nyuengelberg.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-nyuengelberg-corpus": {
      "type": "http",
      "url": "https://corpus.nyuengelberg.org/mcp"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-nyuengelberg-corpus --url 'https://corpus.nyuengelberg.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-nyuengelberg-corpus:
    url: "https://corpus.nyuengelberg.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-nyuengelberg-corpus": {
      "Transport": "http",
      "Url": "https://corpus.nyuengelberg.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-nyuengelberg-corpus -t streamable-http -u 'https://corpus.nyuengelberg.org/mcp'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 67, +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.

### 2026-09-25 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 66, +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.

### 2026-09-22 (score 65, +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.

### 2026-09-19 (score 64, +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.

### 2026-09-17 (score 63, +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.

### 2026-09-15 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (4)

### `search` (~540 tokens)

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);…

Input parameters:

- `query` (string, required)

Output parameters:

- `query` (string)
- `results` (array)

### `fetch` (~125 tokens)

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

Input parameters:

- `id` (string, required)

Output parameters:

- `id` (string)
- `metadata` (object)
- `text`
- `title`
- `url`

### `fetch_document` (~215 tokens)

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)

Input parameters:

- `document_id` (string, required)
- `max_chunks` (integer)
- `start_chunk` (integer)

Output parameters:

- `chunks` (array)
- `document`
- `error` (string)
- `next_start_chunk`
- `returned` (object)
- `total_chunks` (integer)

### `list_documents` (~275 tokens)

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)

Input parameters:

- `cites_case` (string)
- `director` (string)
- `publication_type` (string)

Output parameters:

- `count` (integer)
- `documents` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-nyuengelberg-corpus/corpus#diagnostics

## Score history

- 2026-09-28: 68
- 2026-09-27: 67
- 2026-09-26: 67
- 2026-09-25: 66
- 2026-09-24: 66
- 2026-09-23: 65
- 2026-09-22: 65
- 2026-09-21: 64
- 2026-09-20: 64
- 2026-09-19: 64
- 2026-09-18: 63
- 2026-09-17: 63
- 2026-09-16: 62
- 2026-09-15: 62
- 2026-09-14: 61

## 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.

## Links

- Remote endpoint: https://corpus.nyuengelberg.org/mcp
- Website: https://www.nyuengelberg.org/projects/engelberg-center-corpus/
- Changelog RSS feed: https://verifymcp.io/servers/org-nyuengelberg-corpus/corpus.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-nyuengelberg-corpus/corpus.json
- HTML version of this page: https://verifymcp.io/servers/org-nyuengelberg-corpus/corpus
