Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 11 tools

Disambiguation3/5

Most tools target distinct steps of the intake lifecycle, but two pairs overlap heavily: get_requirements('dpa') and get_dpa_requirements are functionally identical, as are submit_facts and submit_dpa_facts. The descriptions do hint at the generic-versus-specialized split, so an agent can recover, but the boundaries are not crisp and 4 of 11 tools sit in redundant pairs.

Naming Consistency5/5

Every tool follows a clean snake_case verb_noun pattern (get_*, submit_*, list_services, open_matter, request_consultation). No camelCase mixing or vague unqualified verbs; the action is always the first token.

Tool Count4/5

Eleven tools is a sensible scope for a fixed-scope legal intake flow covering listing, opening, requirements, submission, status, payment, terms and delivery. The only slight excess is the duplicated DPA-specific variants, which means two tools do not fully earn their place.

Completeness4/5

The lifecycle is largely covered end to end: discovery, matter creation, requirements, fact submission, status, terms, payment link, consultation fallback and deliverable retrieval. Minor gaps remain — no way to cancel or withdraw a matter, no separate signature/acceptance step, and the final executed PDF/Word is only reachable off-server.

Available Tools

11 tools
get_deliverableFetch the agreementA
Read-only
Inspect

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.

Inputs: matterId (required), matterToken (required).

get_dpa_requirementsFacts needed for a DPAA
Read-only
Inspect

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.

Inputs: role, governingLaw.

get_engagement_termsEngagement termsA
Read-only
Inspect

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

Inputs: tool (required).

get_matter_statusMatter statusC
Read-only
Inspect

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

Inputs: matterId (required), matterToken (required).

get_requirementsFacts needed for a serviceA
Read-only
Inspect

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.

Inputs: service (required), role, governingLaw.

list_servicesList the firm's services for agentsB
Read-only
Inspect

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.

Inputs: no named parameters.

open_matterOpen a matterAInspect

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.

Inputs: tool (required), role, label, receivesPhi, +1 more.

request_consultationAsk for a consultationAInspect

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.

Inputs: name (required), email (required), topic (required).

submit_dpa_factsSend the DPA factsAInspect

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.

Inputs: facts (required), matterId (required), matterToken (required).

submit_factsSend the factsAInspect

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.

Inputs: facts (required), service (required), matterId (required), matterToken (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources