North End Law
Data processing agreement, $350 flat fee, reviewed and released by a lawyer.
Should I use this
Quality & Safety
Findings (4)
- HIGH
- MEDIUMin get_deliverable
- LOWin list_services
- INFOin get_deliverable
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"dpa": {
"url": "https://northend.law/api/mcp"
}
}
}Remote endpoints
https://northend.law/api/mcpstreamable-httpWhat it can do
Tool inventory
Tools (11)
🟢list_services
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.
Input Schema
{
"type": "object",
"properties": {}
}🟢get_requirements(service, governingLaw, role)
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 Schema
{
"type": "object",
"properties": {
"service": {
"type": "string",
"enum": [
"dpa",
"baa"
],
"description": "The service: \"dpa\" (data processing agreement) or \"baa\" (business associate agreement)."
},
"governingLaw": {
"type": "string",
"enum": [
"CALIFORNIA",
"SPAIN"
]
},
"role": {
"type": "string",
"enum": [
"PROCESSOR",
"CONTROLLER",
"BUSINESS_ASSOCIATE"
],
"description": "The client's role."
}
},
"required": [
"service"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_dpa_requirements(governingLaw, role)
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 Schema
{
"type": "object",
"properties": {
"governingLaw": {
"type": "string",
"enum": [
"CALIFORNIA",
"SPAIN"
]
},
"role": {
"type": "string",
"enum": [
"PROCESSOR",
"CONTROLLER"
],
"description": "The client's role."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_engagement_terms(tool)
The full limited-scope engagement text for a service, with its version and SHA-256 hash, and whether it is open for acceptance.
Input Schema
{
"type": "object",
"properties": {
"tool": {
"type": "string",
"enum": [
"dpa",
"baa"
],
"description": "The service: \"dpa\" (data processing agreement) or \"baa\" (business associate agreement)."
}
},
"required": [
"tool"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟡request_consultation(name, email, topic)
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 Schema
{
"type": "object",
"properties": {
"name": {
"type": "string",
"minLength": 2,
"maxLength": 120
},
"email": {
"type": "string",
"format": "email",
"maxLength": 254
},
"topic": {
"type": "string",
"minLength": 3,
"maxLength": 140,
"description": "One line, no confidential facts."
}
},
"required": [
"name",
"email",
"topic"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🔴open_matter(tool, governingLaw, role, receivesPhi, label)
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 Schema
{
"type": "object",
"properties": {
"tool": {
"type": "string",
"enum": [
"dpa",
"baa"
],
"description": "The service: \"dpa\" (data processing agreement) or \"baa\" (business associate agreement)."
},
"governingLaw": {
"type": "string",
"enum": [
"CALIFORNIA",
"SPAIN"
],
"default": "CALIFORNIA",
"description": "The law of the DPA: CALIFORNIA by default, or SPAIN. The law of the BAA: CALIFORNIA only."
},
"role": {
"type": "string",
"enum": [
"PROCESSOR",
"CONTROLLER",
"BUSINESS_ASSOCIATE"
],
"description": "The client's role under the agreement: PROCESSOR by default, or CONTROLLER. For a BAA: BUSINESS_ASSOCIATE (the default and the only role offered)."
},
"receivesPhi": {
"type": "boolean",
"description": "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, use request_consultation."
},
"label": {
"type": "string",
"maxLength": 60,
"description": "Optional. A short label for the user to recognize the request, for example \"customer DPA, October\". It must name no one."
}
},
"required": [
"tool"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_matter_status(matterId, matterToken)
Where the matter stands, the next human step, the target in business hours, and any question from the lawyer.
Input Schema
{
"type": "object",
"properties": {
"matterId": {
"type": "string",
"description": "The matter id returned by open_matter."
},
"matterToken": {
"type": "string",
"description": "The matter token returned once by open_matter."
}
},
"required": [
"matterId",
"matterToken"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_payment_link(matterId, matterToken)
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 Schema
{
"type": "object",
"properties": {
"matterId": {
"type": "string",
"description": "The matter id returned by open_matter."
},
"matterToken": {
"type": "string",
"description": "The matter token returned once by open_matter."
}
},
"required": [
"matterId",
"matterToken"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟡submit_facts(service, matterId, matterToken, 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 Schema
{
"type": "object",
"properties": {
"service": {
"type": "string",
"enum": [
"dpa",
"baa"
],
"description": "The service: \"dpa\" (data processing agreement) or \"baa\" (business associate agreement)."
},
"matterId": {
"type": "string",
"description": "The matter id returned by open_matter."
},
"matterToken": {
"type": "string",
"description": "The matter token returned once by open_matter."
},
"facts": {
"type": "object",
"additionalProperties": {},
"description": "The fact package; see get_requirements."
}
},
"required": [
"service",
"matterId",
"matterToken",
"facts"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟡submit_dpa_facts(matterId, matterToken, 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 Schema
{
"type": "object",
"properties": {
"matterId": {
"type": "string",
"description": "The matter id returned by open_matter."
},
"matterToken": {
"type": "string",
"description": "The matter token returned once by open_matter."
},
"facts": {
"type": "object",
"additionalProperties": {},
"description": "The fact package; see get_dpa_requirements."
}
},
"required": [
"matterId",
"matterToken",
"facts"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_deliverable(matterId, matterToken)
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 Schema
{
"type": "object",
"properties": {
"matterId": {
"type": "string",
"description": "The matter id returned by open_matter."
},
"matterToken": {
"type": "string",
"description": "The matter token returned once by open_matter."
}
},
"required": [
"matterId",
"matterToken"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Evidence