mcpbeat Sign in

Corpus MCP Server

by nyuengelberg Your server? Claim it
answering

Corpus is answering right now. Last checked 10 min ago. It exposes 4 tools.

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

Uptime history 9 days of history
9 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
283 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Corpus every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add corpus --transport http https://corpus.nyuengelberg.org/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "corpus": {
      "url": "https://corpus.nyuengelberg.org/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.corpus]
url = "https://corpus.nyuengelberg.org/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "corpus": {
      "url": "https://corpus.nyuengelberg.org/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "corpus": {
      "url": "https://corpus.nyuengelberg.org/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

document
fetch_document
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)
documents
list_documents
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)
fetch
fetch
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
search
search
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); "draft_pdf_page" is a draft's page (never a journal pin cite); null means online-only — cite by URL. - 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

Endpoints

URLTransportStateLatencyChecked
https://corpus.nyuengelberg.org/mcp streamable-http answering 183 ms 10 min ago

Alternatives to Corpus

same job, measured the same way
Soma
by medianemi-beep

Execution-verified code generation and verification with signed, offline-checkable certificates.

24 installs/wk local only
PeopleSearch.im
by peoplesearch

Plain-English people search with verified work emails, email verification and LinkedIn lookup.

12 tools answering
Baton
by vinsenzo83

Hand off AI work with a signed Verification Receipt — an independent verifier proves it runs.

38 installs/wk 45 tools answering
Ie Eli MCP
by matematicsolutions

MCP server for the Irish Statute Book: acts and SIs with verifiable ELI citations.

210 installs/wk local only
Planka MCP
by omnicoreos

Planka 2.x MCP server with verified card, task, comment, label, and list operations.

33 installs/wk local only
Mt Eli MCP
by matematicsolutions

MCP server for Maltese legislation (legislation.mt) with ELI and verifiable citations.

239 installs/wk local only
Sk Eli MCP
by matematicsolutions

MCP server for Slovak legislation (Slov-lex) with ELI and verifiable citations.

193 installs/wk local only
Lightbringer
by lightbringer

Register innovations, request patent preparation, and collaborate with Lightbringer’s patent team.

20 tools answering

Corpus — questions

Answers built from our own checks of this server.

What can Corpus do?
It exposes 4 tools, read directly from the server on our last check. Among them: fetch, fetch_document, list_documents, search. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Corpus working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 283 ms. The bar chart above shows every period we have measured.
How do I connect Corpus?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Corpus need an API key?
No. Corpus completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Corpus?
It answers our handshake in 283 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.