# North End Law (remote · northend.law)

Data processing agreement, $350 flat fee, reviewed and released by a lawyer.

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

## Components

- remote · `northend.law`: 71/100 (this document), [markdown](https://verifymcp.io/servers/law-northend-dpa/api-mcp.md), [page](https://verifymcp.io/servers/law-northend-dpa/api-mcp)

## Channel facts

- Endpoint: `https://northend.law/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **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 5 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**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1717 tokens (~156/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 44/100
  - Stability check failed: schema churn in the 15 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 85% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the North End Law MCP server?

North End Law is a hosted endpoint at https://northend.law/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.

### Claude

```bash
claude mcp add --transport http law-northend-dpa 'https://northend.law/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "law-northend-dpa": {
      "url": "https://northend.law/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "law-northend-dpa": {
      "type": "http",
      "url": "https://northend.law/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.law-northend-dpa]
url = "https://northend.law/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "law-northend-dpa": {
      "type": "remote",
      "url": "https://northend.law/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add law-northend-dpa --url 'https://northend.law/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  law-northend-dpa:
    url: "https://northend.law/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "law-northend-dpa": {
      "Transport": "http",
      "Url": "https://northend.law/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add law-northend-dpa -t streamable-http -u 'https://northend.law/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "law-northend-dpa": {
      "type": "http",
      "url": "https://northend.law/api/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-10-22 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 41 to 44.

### 2026-10-20 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 34 to 38.

### 2026-10-18 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 28 to 31.

### 2026-10-16 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 21 to 24.

### 2026-10-14 (score 67, 0)

- [security regression] Stability: 0.20 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security improvement] Judged manipulation: unverified → pass
- [security] Tool “submit_facts” rewrote its description, which is the text the model reads
- [security] Tool “get_deliverable” rewrote its description, which is the text the model reads
- [security] Tool “open_matter” rewrote its description, which is the text the model reads
- [security] Tool “submit_dpa_facts” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 132 → 156
- [functional regression] “open_matter” dropped the required parameter “adverseParties”
- [functional regression] “open_matter” dropped the required parameter “client”
- [functional regression] “open_matter” dropped the required parameter “counterparties”
- [functional regression] “open_matter” dropped the required parameter “namedPerson”
- [cosmetic] “open_matter” added an optional parameter “label”

### 2026-10-12 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 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-10-10 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 10. That category is still filling its 30-day observation window: 1 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-10-08 (score 65)

First indexed and scored.

## MCP tools (11)

### `list_services` (~75 tokens)

List the firm's services for agents

What North End Law offers through this server, at what fixed price, under which laws, and who is responsible. Responsible lawyer: Sergio Maldonado Elvira, Founder & Principal Attorney, North End Law Corporation, 447 Sutter St. Suite 506 - 1349, San Francisco, California 94108, United States.

### `get_requirements` (~111 tokens)

Facts needed for a service

The facts a service needs, as a JSON Schema: service "dpa" (data processing agreement) or "baa" (business associate agreement). For a DPA, optionally narrowed to one governing law and the client's role. Do not send the facts until the engagement has begun.

Input parameters:

- `governingLaw` (string)
- `role` (string): The client's role.
- `service` (string, required): The service: "dpa" (data processing agreement) or "baa" (business associate agreement).

### `get_dpa_requirements` (~65 tokens)

Facts needed for a DPA

The facts the data processing agreement needs, as a JSON Schema. Optionally narrowed to one governing law and the client's role. Do not send the facts until the engagement has begun.

Input parameters:

- `governingLaw` (string)
- `role` (string): The client's role.

### `get_engagement_terms` (~65 tokens)

Engagement terms

The full limited-scope engagement text for a service, with its version and SHA-256 hash, and whether it is open for acceptance.

Input parameters:

- `tool` (string, required): The service: "dpa" (data processing agreement) or "baa" (business associate agreement).

### `request_consultation` (~71 tokens)

Ask for a consultation

For anything outside the listed services: gives the booking link and lets the firm know a person would like to talk. Send a one-line topic only, no confidential facts.

Input parameters:

- `email` (string, required)
- `name` (string, required)
- `topic` (string, required): One line, no confidential facts.

### `open_matter` (~491 tokens)

Open a matter

Starts a request for a data processing agreement ($350) or, with tool "baa", a business associate agreement ($350). Send only the service, the governing law (CALIFORNIA by default, or SPAIN; CALIFORNIA only for a BAA), the client's role (PROCESSOR by default, or CONTROLLER; BUSINESS_ASSOCIATE for a BAA, with receivesPhi false) and, if useful, a short label that names no one. Do not ask the user for, and do not send, any name, e-mail address or postal address: the firm never needs them from you. Write "the Client" for the user's company and "the Customer" (or "the Vendor", when the client is the controller) for the other party. Returns a matter id, a matter token (shown once: keep it) and a private link. Give the private link to the user and ask them to open it in their browser within 24 hours. There the user enters their company's details, their own and the other party's, and the firm runs its conflicts check. You never see those details. The firm accepts the engagement when its automatic conflicts check is clear and payment is received (for a subscriber, when the engagement is accepted and the check is clear). If a possible conflict is found, nothing is charged, or the payment is refunded in full. A vendor whose services handle protected health information should use request_consultation.

Input parameters:

- `governingLaw` (string): The law of the DPA: CALIFORNIA by default, or SPAIN. The law of the BAA: CALIFORNIA only.
- `label` (string): Optional. A short label for the user to recognize the request, for example "customer DPA, October". It must name no one.
- `receivesPhi` (boolean): BAA only, and required for it: whether the client's services are designed to create, receive, maintain or transmit protected health information. Only false is accepted; for services that handle it, u…
- `role` (string): The client's role under the agreement: PROCESSOR by default, or CONTROLLER. For a BAA: BUSINESS_ASSOCIATE (the default and the only role offered).
- `tool` (string, required): The service: "dpa" (data processing agreement) or "baa" (business associate agreement).

### `get_matter_status` (~66 tokens)

Matter status

Where the matter stands, the next human step, the target in business hours, and any question from the lawyer.

Input parameters:

- `matterId` (string, required): The matter id returned by open_matter.
- `matterToken` (string, required): The matter token returned once by open_matter.

### `get_payment_link` (~97 tokens)

Payment link

The firm's own card payment page for $350, available once the named person has accepted the engagement. The fee is charged in full at checkout and refunded in full if the firm declines the matter or does not deliver. The link is also e-mailed to the named person.

Input parameters:

- `matterId` (string, required): The matter id returned by open_matter.
- `matterToken` (string, required): The matter token returned once by open_matter.

### `submit_facts` (~258 tokens)

Send the facts

The fact package for the matter's service, in the "dealroom.solo-intake/1" shape described by get_requirements. Accepted only once the engagement has begun, and again when the lawyer asks for changes. Leave out counterpartyLegalName: the firm adds the other party from the private page. Do not ask the user for, and do not send, any name, e-mail address or postal address: the firm never needs them from you. Write "the Client" for the user's company and "the Customer" (or "the Vendor", when the client is the controller) for the other party. A fact package that contains a name, an e-mail address or a postal address the firm holds for the matter is refused. For a business associate agreement, the facts must not contain protected health information: they describe the services, not any individual.

Input parameters:

- `facts` (object, required): The fact package; see get_requirements.
- `matterId` (string, required): The matter id returned by open_matter.
- `matterToken` (string, required): The matter token returned once by open_matter.
- `service` (string, required): The service: "dpa" (data processing agreement) or "baa" (business associate agreement).

### `submit_dpa_facts` (~211 tokens)

Send the DPA facts

The fact package for the agreement, in the "dealroom.solo-intake/1" shape described by get_dpa_requirements. Accepted only once the engagement has begun, and again when the lawyer asks for changes. Leave out counterpartyLegalName: the firm adds the other party from the private page. Do not ask the user for, and do not send, any name, e-mail address or postal address: the firm never needs them from you. Write "the Client" for the user's company and "the Customer" (or "the Vendor", when the client is the controller) for the other party. A fact package that contains a name, an e-mail address or a postal address the firm holds for the matter is refused.

Input parameters:

- `facts` (object, required): The fact package; see get_dpa_requirements.
- `matterId` (string, required): The matter id returned by open_matter.
- `matterToken` (string, required): The matter token returned once by open_matter.

### `get_deliverable` (~112 tokens)

Fetch the agreement

Once a lawyer has released it: the agreement in Markdown with placeholders ([Client], [Customer] or [Vendor], and blank addresses and signatures), so you can explain it to the user. The final agreement with the parties' details, in PDF and Word, is only on the private page and in the e-mail to the person who signs.

Input parameters:

- `matterId` (string, required): The matter id returned by open_matter.
- `matterToken` (string, required): The matter token returned once by open_matter.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/law-northend-dpa/api-mcp#diagnostics

## Score history

- 2026-10-22: 71
- 2026-10-21: 70
- 2026-10-20: 70
- 2026-10-19: 69
- 2026-10-18: 69
- 2026-10-17: 68
- 2026-10-16: 68
- 2026-10-15: 67
- 2026-10-14: 67
- 2026-10-13: 67
- 2026-10-12: 67
- 2026-10-10: 66
- 2026-10-08: 65

## Common questions

### What is the North End Law MCP server?

North End Law is an MCP server listed in the public MCP registry as law.northend/dpa. Data processing agreement, $350 flat fee, reviewed and released by a lawyer. This page covers its hosted endpoint (https://northend.law/api/mcp).

### Is the North End Law MCP server safe to use?

North End Law scores 71 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 North End Law MCP server expose?

North End Law exposes 11 tools: list_services, get_requirements, get_dpa_requirements, get_engagement_terms, request_consultation, and 6 more. Their descriptions and schemas cost roughly 1,622 tokens of context every time the server is loaded.

### Does the North End Law MCP server require authentication?

No. We connected to North End Law without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the North End Law MCP server still maintained?

North End Law is still listed as active in the MCP registry. We last reached this channel on 22 October 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://northend.law/api/mcp
- Website: https://northend.law/agents
- Changelog RSS feed: https://verifymcp.io/servers/law-northend-dpa/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/law-northend-dpa/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/law-northend-dpa/api-mcp