North End Law MCP server
law.northend/dpanorthend.lawstreamable-httpv1.0.0Scanned
Data processing agreement, $350 flat fee, reviewed and released by a lawyer.
11 tools: 4 change things and 7 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the North End Law MCP server can do
The North End Law MCP server is published by northend.law, a domain the MCP Registry verified. It has 11 tools. It can create or change data (4 tools: request_consultation, open_matter, submit_facts and submit_dpa_facts), but cannot delete data. 7 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (tool-shadowing). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Changes things 4Claude Code: ask
open_matterStarts a request for a data processing agreement ($350) or, with tool "baa", a business associate agreement ($350).1 finding
Why it is in this group
- The name "open_matter" says "open": a word for a change.
Findings
- Warn
The description names a tool "baa" that this server does not list.
What this check looks forMatched text
description: "...ta processing agreement ($350) or, with tool "baa", a business associate agreement ($350)...."
Description, as the server wrote it 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.
request_consultationFor anything outside the listed services: gives the booking link and lets the firm know a person would like to talk.No findings
Why it is in this group
- The name "request_consultation" says "request": a word for a change.
Description, as the server wrote it 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.
submit_dpa_factsThe fact package for the agreement, in the "dealroom.solo-intake/1" shape described by get_dpa_requirements.No findings
Why it is in this group
- The name "submit_dpa_facts" says "submit": a word for a change.
Description, as the server wrote it 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.
submit_factsThe fact package for the matter's service, in the "dealroom.solo-intake/1" shape described by get_requirements.No findings
Why it is in this group
- The name "submit_facts" says "submit": a word for a change.
Description, as the server wrote it 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.
Only reads 7Show 7 read-only tools
get_deliverableOnce 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…No findings
Why it is in this group
- The name "get_deliverable" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
get_dpa_requirementsThe facts the data processing agreement needs, as a JSON Schema.No findings
Why it is in this group
- The name "get_dpa_requirements" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
get_engagement_termsThe full limited-scope engagement text for a service, with its version and SHA-256 hash, and whether it is open for acceptance.No findings
Why it is in this group
- The name "get_engagement_terms" says "get": a word for reading.
Description, as the server wrote it The full limited-scope engagement text for a service, with its version and SHA-256 hash, and whether it is open for acceptance.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_matter_statusWhere the matter stands, the next human step, the target in business hours, and any question from the lawyer.No findings
Why it is in this group
- The name "get_matter_status" says "get": a word for reading.
Description, as the server wrote it Where the matter stands, the next human step, the target in business hours, and any question from the lawyer.
Annotations the server declares
- readOnlyHint: true
get_payment_linkThe firm's own card payment page for $350, available once the named person has accepted the engagement.No findings
Why it is in this group
- The name "get_payment_link" says "get": a word for reading.
Description, as the server wrote it 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.
get_requirementsThe facts a service needs, as a JSON Schema: service "dpa" (data processing agreement) or "baa" (business associate agreement).No findings
Why it is in this group
- The name "get_requirements" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
list_servicesWhat North End Law offers through this server, at what fixed price, under which laws, and who is responsible.No findings
Why it is in this group
- The name "list_services" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:15 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://northend.law/api/mcp: tools/list returned 11 tools to an anonymous client, including request_consultation (write), open_matter (write), submit_facts (write), submit_dpa_facts (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnopen_matter
The description names a tool "baa" that this server does not list.
What this check looks forMatched text
description: "...ta processing agreement ($350) or, with tool "baa", a business associate agreement ($350)...."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools10 changed.~10 changedView diff
- Changed:get_deliverableOnly readsinputSchema
- Changed:get_dpa_requirementsOnly readsinputSchema
- Changed:get_engagement_termsOnly readsinputSchema
- Changed:get_matter_statusOnly readsinputSchema
- Changed:get_payment_linkOnly readsinputSchema
- Changed:get_requirementsOnly readsinputSchema
- Changed:open_matterChanges thingsinputSchema
- Changed:request_consultationChanges thingsinputSchema
- Changed:submit_dpa_factsChanges thingsinputSchema
- Changed:submit_factsChanges thingsinputSchema
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http dpa https://northend.law/api/mcpclaude mcp add --transport http dpa https://northend.law/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__dpa__list_services",
"mcp__dpa__get_requirements",
"mcp__dpa__get_dpa_requirements",
"mcp__dpa__get_engagement_terms",
"mcp__dpa__get_matter_status",
"mcp__dpa__get_payment_link",
"mcp__dpa__get_deliverable"
],
"ask": [
"mcp__dpa__request_consultation",
"mcp__dpa__open_matter",
"mcp__dpa__submit_facts",
"mcp__dpa__submit_dpa_facts"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dpa. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/law.northend/dpa/verify?hash=2ff8fe199b837e194354661950e4f976a70056df22bec6d5fb1255ab2236869a" | jq -e '.changed == false'Pinned hash 2ff8fe199b83, from Nov 18, 2026, 17:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/law.northend/dpa/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/law.northend/dpa)Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.
North End Law MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the North End Law MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the North End Law MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the North End Law MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the North End Law MCP server have?
- 11 tools: 4 write, 7 read. request_consultation, open_matter, submit_facts, submit_dpa_facts, list_services, get_requirements, get_dpa_requirements, get_engagement_terms and 3 more.
Does the North End Law MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the North End Law MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the North End Law MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 4, 2026. Every change is on this page and in its Atom feed.