Open Agreements
REMOTE · OPENAGREEMENTS.ORG · 2 COMPONENTS · SCANNED SEP 20
Fill standard legal agreement templates (NDAs, SAFEs, NVCA docs, employment) as DOCX files.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 516 tokens (~129/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 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the Open Agreements MCP server?
Open Agreements is a hosted endpoint at https://openagreements.org/api/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 · openagreements.org
claude mcp add --transport http open-agreements-open-agreements 'https://openagreements.org/api/mcp'
{
"mcpServers": {
"open-agreements-open-agreements": {
"url": "https://openagreements.org/api/mcp"
}
}
} {
"servers": {
"open-agreements-open-agreements": {
"type": "http",
"url": "https://openagreements.org/api/mcp"
}
}
} [mcp_servers.open-agreements-open-agreements] url = "https://openagreements.org/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"open-agreements-open-agreements": {
"type": "remote",
"url": "https://openagreements.org/api/mcp",
"enabled": true
}
}
} openclaw mcp add open-agreements-open-agreements --url 'https://openagreements.org/api/mcp' --transport streamable-http
mcp_servers:
open-agreements-open-agreements:
url: "https://openagreements.org/api/mcp" {
"McpServers": {
"open-agreements-open-agreements": {
"Transport": "http",
"Url": "https://openagreements.org/api/mcp"
}
}
} assistant mcp add open-agreements-open-agreements -t streamable-http -u 'https://openagreements.org/api/mcp'
{
"mcpServers": {
"open-agreements-open-agreements": {
"type": "http",
"url": "https://openagreements.org/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://openagreements.org/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=openagreements.org | CN=YR2,O=Let's Encrypt,C=US | 30 Jul 2026 | 28 Oct 2026 | RSA 2048 | SHA256-RSA | 6e559c0146deb43ead4735c2eb5ff7f9a6d |
| SANs: openagreements.org | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of openagreements.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| openagreements.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=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://openagreements.org/api/mcp | Verified | 200 | |
| http (plaintext) | http://openagreements.org/api/mcp | HTTPS enforced | 308 | https://openagreements.org/api/mcp |
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 →
fill_template ~168
Fill a legal agreement template with field values and return a document via URL or MCP resource preview metadata. For field-selector templates (e.g. NVCA), also generates a redline (track-changes) document comparing the filled output against the standard form.
| Name | Type | Req | Description |
|---|---|---|---|
| include_redline | boolean | – | Generate a redline (track-changes) document. Defaults to true for field-selectors. |
| redline_base | string | – | Base document for redline comparison. "source" = raw standard form (default), "clean" = cleaned intermediate. |
| return_mode | string | – | Artifact return mode. Defaults to "url". |
| template | string | yes | Template ID, e.g. "common-paper-mutual-nda". |
| values | object | – | Field values to fill in the template. |
No output schema declared.
No examples provided.
get_template ~39
Fetch a single template definition with full 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_templates ~105
List all available legal agreement 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. For finding templates by topic, jurisdiction, or source, use search_templates instead.
| 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.
search_templates ~204
Search for legal agreement templates by keyword. Uses BM25 ranking to find the most relevant templates matching your query. Searches across template names, descriptions, categories, sources, and field definitions. Use this instead of list_templates when you know what kind of agreement you need.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter (exact, case-insensitive). Values: confidentiality, employment, sales-licensing, data-compliance, deals-partnerships, professional-services, venture-financing, other. |
| max_results | number | – | Maximum results to return (1-50, default 10). |
| query | string | yes | Search query. Examples: "NDA", "employment offer letter", "NVCA stock purchase", "data processing GDPR", "non-compete Wyoming". |
| source | string | – | Optional source filter (exact, case-insensitive). Values: "Common Paper", "Bonterms", "Y Combinator", "NVCA", "OpenAgreements". |
No output schema declared.
No examples provided.
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 hosted endpoint (https://openagreements.org/api/mcp).
Is the Open Agreements MCP server safe to use?
Open Agreements scores 88 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 Open Agreements MCP server expose?
Open Agreements exposes 4 tools: list_templates, search_templates, get_template, fill_template. Their descriptions and schemas cost roughly 516 tokens of context every time the server is loaded.
Does the Open Agreements MCP server require authentication?
No. We connected to Open Agreements without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.