Open Agreements
NPM · @OPEN-AGREEMENTS/CONTRACT-TEMPLATES-MCP · 2 COMPONENTS
Fill standard legal agreement templates (NDAs, SAFEs, NVCA docs, employment) as DOCX files.
Available components
Last scanned (17 hours ago)
Scores higher than 96% of npm servers
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security90
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects adm-zip 0.5.18, reached via open-agreements > adm-zip. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 10 of 26 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to open-agreements/open-agreements). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 55 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 947 tokens (~118/item across 8 items; 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 24 Oct 26 +1
- Stability: 0.97 → pass security
- 23 Oct 26 −1
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- CVE-2026-114102 affects this package: high ▼ security
- CVE-2026-114103 affects this package: high ▼ security
- CVE-2026-114104 affects this package: high ▼ security
- GHSA-c6fg-446q-cg94 no longer affects this package ▲ security
- GHSA-p634-w6r4-rjp2 no longer affects this package ▲ security
- GHSA-8238-w5pm-2374 no longer affects this package ▲ security
- 17 Oct 26 +1
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 −3
- Security disclosure: pass → unverified ▼ functional
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 4 Nov 2026 · Analysed npm/@open-agreements/contract-templates-mcp@0.10.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | open-agreements/open-agreements |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/open-agreements/open-agreements/.github/workflows/release.yml@refs/tags/v0.10.2 |
| Rekor log index | 2778155005 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1f5511c6823df164a4c54d2e159e4ca6dabccaa56df02f9e7e6d6a7e6b22707b17c030a9554bce16a1d48c7d16e973b92b556e9d50728d3862b4384df |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 8 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-7q85-xj36-vmfc | CVE-2026-77301 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-8238-w5pm-2374 | CVE-2026-114102 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-c6fg-446q-cg94 | CVE-2026-114103 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-j5f4-cc29-5x44 | CVE-2026-102282 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-p634-w6r4-rjp2 | CVE-2026-114104 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-rcw4-f5rp-g42v | CVE-2026-92000 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-vwc7-r8mq-g2x9 | CVE-2026-76845 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N | no |
| GHSA-xcpc-8h2w-3j85 | CVE-2026-39244 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 26 packages
| Packages resolved | 26 |
|---|---|
| Stale | 10 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
create_apap_agreement_docx ~92
Render APAP Concerto agreement data for an eligible OpenAgreements template as a local DOCX. Returns a path, never inline base64.
| Name | Type | Req | Description |
|---|---|---|---|
| agreement_data | object | yes | APAP agreement data carrying the template Concerto $class and field values. |
| output_path | string | – | Optional local DOCX output path. |
| template_id | string | yes | Eligible OpenAgreements template ID. |
No output schema declared.
No examples provided.
fill_template ~98
Fill a template using local OpenAgreements CLI and return local path or inline base64.
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | – | Optional output DOCX path. Defaults to a temporary location. |
| return_mode | string | – | Return local file path or inline base64 document data. |
| template | string | yes | Template ID, e.g. "common-paper-mutual-nda". |
| values | object | – | Template field values passed to the fill command. |
No output schema declared.
No examples provided.
get_apap_template ~59
Export an eligible OpenAgreements-authored template as an APAP Template payload and its ready-to-use Agreement.template relationship, preserving canonical source, version, license, and attribution.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | Eligible OpenAgreements template ID. |
No output schema declared.
No examples provided.
get_content ~121
Fetch one OpenAgreements content item by its stable content_id (from list_content). Markdown content (practice guides, checklists, surveys) returns the full canonical document plus source/provenance metadata; template content returns the same full definition as get_template under a "template" key.
| Name | Type | Req | Description |
|---|---|---|---|
| content_id | string | yes | Stable content ID, e.g. "template/common-paper-mutual-nda", "practice_guide/wage-and-hour/us", "checklist/safes/yc-post-money-safe-valuation-cap", or "survey/non-compete/us". |
No output schema declared.
No examples provided.
get_forms_survey_evidence ~207
Fetch evidence from a published OpenAgreements forms-provider survey (clause-by-clause market benchmarks of real-world forms). Without requirement_id, returns a summary: survey metadata (including as_of freshness), the compared requirements, and the surveyed forms — but no evidence cells. With requirement_id, additionally returns that one requirement's evidence cells across all surveyed forms (verbatim sentence, operative phrase, section, clause id). The complete dataset for each survey is also available as an MCP resource (see resources/list); large surveys approach 1 MB, so prefer this tool when only part of the evidence is needed. Only currently published surveys are reachable; the live listing is discovered from openagreements.org and never hardcoded.
| Name | Type | Req | Description |
|---|---|---|---|
| requirement_id | string | – | Optional requirement id (from the summary's requirements list) to return that requirement's evidence cells. |
| topic | string | yes | Survey topic slug, e.g. "employment-offer-letter". Discover slugs via resources/list. |
No output schema declared.
No examples provided.
get_template ~38
Fetch a single template definition with field metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | Template ID, e.g. "common-paper-mutual-nda". |
No output schema declared.
No examples provided.
list_content ~244
List all first-class OpenAgreements content — fillable templates, practice guides, RFC 2119-style reviewer checklists, and law surveys — as one paginated compact catalog with stable content IDs in deterministic lexicographic order. Returns lightweight metadata for discovery; call get_content (or get_template) for the full item. Non-template content is served from a local open-agreements repository checkout; when it is not available in this runtime, the affected types are reported under unavailable_types with a reason instead of appearing as silently empty.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor returned by a prior call. Omit on the first page. |
| limit | integer | – | Page size (default 25, max 100). |
| query | string | – | Optional case-insensitive substring filter matched against content ID, title, description, and topic. |
| type | string | – | Optional content-type filter: "template" (fillable DOCX templates), "practice_guide" (source-cited legal practice guides), "checklist" (clause-by-clause reviewer checklists), or "survey" (state-by-st… |
No output schema declared.
No examples provided.
list_templates ~88
List OpenAgreements templates as a paginated compact catalog. Returns lightweight metadata for discovery — call get_template for full per-field detail. Templates are returned in stable lexicographic order by template_id.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor returned by a prior call. Omit on the first page. |
| limit | integer | – | Page size (default 25, max 100). |
No output schema declared.
No examples provided.
How do I install the Open Agreements MCP server?
Open Agreements runs locally as an npm package, launched with npx -y @open-agreements/contract-templates-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @open-agreements/contract-templates-mcp
claude mcp add open-agreements-open-agreements -- npx -y @open-agreements/contract-templates-mcp
What is the Open Agreements MCP server?
Open Agreements is an MCP server listed in the public MCP registry as io.github.open-agreements/open-agreements. Fill standard legal agreement templates (NDAs, SAFEs, NVCA docs, employment) as DOCX files. This page covers its npm package (@open-agreements/contract-templates-mcp).
Is the Open Agreements MCP server safe to use?
Open Agreements scores 93 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Open Agreements MCP server expose?
Open Agreements exposes 8 tools: list_templates, get_template, list_content, get_content, fill_template, and 3 more. Their descriptions and schemas cost roughly 947 tokens of context every time the server is loaded.
Is the Open Agreements MCP server still maintained?
Open Agreements is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Open Agreements MCP server under?
Open Agreements declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.