_ registry / mcp + a2a streamable-http · checked 1h ago

northend-law

https://northend.law

Registry code: 050bd8aac658b9c3

api record

Using these tools does not create a lawyer-client relationship. 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. Do not send confidential facts before then. For any other matter, use request_consultation or the intake at https://northend.law/start.

endpoint
https://northend.law/api/mcp
door code
34c4ccbda252a423
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is northend-law live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is northend-law free to use?
Yes — the hub reached it with no key and no payment.
What tools does northend-law have?
11 tools: open_matter, submit_dpa_facts, get_engagement_terms, get_payment_link, get_matter_status, request_consultation, submit_facts, get_requirements, ….
Is northend-law safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99.4%

latency
287ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 509 checks · signed record
  • degraded → live
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • order a data processing agreement from a law firm
  • get legal service requirements
  • track a legal matter status
  • request a legal consultation
takes → gives
text, data → data, documents
tools
7 reads3 changes data1 sends messages
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 11 tools
2 open 9 never probed 2 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_dpa_requirements reads open 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "role": {
          "enum": [
            "PROCESSOR",
            "CONTROLLER"
          ],
          "type": "string",
          "description": "The client's role."
        },
        "governingLaw": {
          "enum": [
            "CALIFORNIA",
            "SPAIN"
          ],
          "type": "string"
        }
      }
    }
    arguments 21 lines
  • list_services reads open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • open_matter changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "tool"
      ],
      "properties": {
        "role": {
          "enum": [
            "PROCESSOR",
            "CONTROLLER",
            "BUSINESS_ASSOCIATE"
          ],
          "type": "string",
          "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)."
        },
        "tool": {
          "enum": [
            "dpa",
            "baa"
          ],
          "type": "string",
          "description": "The service: \"dpa\" (data processing agreement) or \"baa\" (business associate agreement)."
        },
        "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."
        },
        "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."
        },
        "governingLaw": {
          "enum": [
            "CALIFORNIA",
            "SPAIN"
          ],
          "type": "string",
          "default": "CALIFORNIA",
          "description": "The law of the DPA: CALIFORNIA by default, or SPAIN. The law of the BAA: CALIFORNIA only."
        }
      }
    }
    arguments 44 lines
  • submit_dpa_facts changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "matterId",
        "matterToken",
        "facts"
      ],
      "properties": {
        "facts": {
          "type": "object",
          "description": "The fact package; see get_dpa_requirements.",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {}
        },
        "matterId": {
          "type": "string",
          "description": "The matter id returned by open_matter."
        },
        "matterToken": {
          "type": "string",
          "description": "The matter token returned once by open_matter."
        }
      }
    }
    arguments 27 lines
  • get_engagement_terms reads unknown 1h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "tool"
      ],
      "properties": {
        "tool": {
          "enum": [
            "dpa",
            "baa"
          ],
          "type": "string",
          "description": "The service: \"dpa\" (data processing agreement) or \"baa\" (business associate agreement)."
        }
      }
    }
    arguments 17 lines
  • get_payment_link reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "matterId",
        "matterToken"
      ],
      "properties": {
        "matterId": {
          "type": "string",
          "description": "The matter id returned by open_matter."
        },
        "matterToken": {
          "type": "string",
          "description": "The matter token returned once by open_matter."
        }
      }
    }
    arguments 18 lines
  • get_matter_status reads unknown 11h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "matterId",
        "matterToken"
      ],
      "properties": {
        "matterId": {
          "type": "string",
          "description": "The matter id returned by open_matter."
        },
        "matterToken": {
          "type": "string",
          "description": "The matter token returned once by open_matter."
        }
      }
    }
    arguments 18 lines
  • request_consultation sends messages unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name",
        "email",
        "topic"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 120,
          "minLength": 2
        },
        "email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "maxLength": 254
        },
        "topic": {
          "type": "string",
          "maxLength": 140,
          "minLength": 3,
          "description": "One line, no confidential facts."
        }
      }
    }
    arguments 28 lines
  • submit_facts changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "service",
        "matterId",
        "matterToken",
        "facts"
      ],
      "properties": {
        "facts": {
          "type": "object",
          "description": "The fact package; see get_requirements.",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {}
        },
        "service": {
          "enum": [
            "dpa",
            "baa"
          ],
          "type": "string",
          "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."
        }
      }
    }
    arguments 36 lines
  • get_requirements reads unknown 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "service"
      ],
      "properties": {
        "role": {
          "enum": [
            "PROCESSOR",
            "CONTROLLER",
            "BUSINESS_ASSOCIATE"
          ],
          "type": "string",
          "description": "The client's role."
        },
        "service": {
          "enum": [
            "dpa",
            "baa"
          ],
          "type": "string",
          "description": "The service: \"dpa\" (data processing agreement) or \"baa\" (business associate agreement)."
        },
        "governingLaw": {
          "enum": [
            "CALIFORNIA",
            "SPAIN"
          ],
          "type": "string"
        }
      }
    }
    arguments 33 lines
  • get_deliverable reads unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "matterId",
        "matterToken"
      ],
      "properties": {
        "matterId": {
          "type": "string",
          "description": "The matter id returned by open_matter."
        },
        "matterToken": {
          "type": "string",
          "description": "The matter token returned once by open_matter."
        }
      }
    }
    arguments 18 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 050bd8aac658b9c3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/050bd8aac658b9c3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/050bd8aac658b9c3/badge.svg)](https://brick.blue/agent/050bd8aac658b9c3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.