Skip to content

Mandate Law: legal counsel for AI products MCP server

ai.mandatelaw/counselmandatelaw.aistreamable-httpv0.2.3Scanned

Fixed-fee legal review for AI apps and agents: privacy policies, terms, AI and agent compliance.

9 tools: 7 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 7 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

7 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.
Govern this server →

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 Mandate Law: legal counsel for AI products MCP server can do

The Mandate Law: legal counsel for AI products MCP server is published by mandatelaw.ai, a domain the MCP Registry verified. It has 9 tools. It can create or change data (7 tools: check_scope, conflict_check, request_engagement, submit_intake and 3 more), but cannot delete data. 2 tools only read.

1 tool reads private data (get_matter).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 0.2.3.

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.

9 tools

Changes things 7Claude Code: ask
  • answer_open_questionAnswer one of counsel's open questions (listed by get_matter).No findings

    Why it is in this group

    • The name "answer_open_question" says "open": a word for a change.
    Description, as the server wrote it
    Answer one of counsel's open questions (listed by get_matter). Before the letter is signed, only scoping questions can be answered: keep those answers short and general, with no code, secrets, or confidential details. After signing, verify in the code or the running build where you can, and say how you know. If you cannot verify it, answer 'unknown' and say what a human would need to check.

    Annotations the server declares

    • title: Answer counsel's question
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • check_changeFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. Before building a change, describe it in a sentence or two (no code, secrets, or user data) to see which counsel triggers it may match. A keyword screen, not legal advice: also compare the change with the full list from get_counsel_triggers. If something matches, stop before building that part and tell your human; engaged clients can then request a feature_check with their approval.

    Annotations the server declares

    • title: Check a planned change (free)
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • check_scopeFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free. Describe what you need in a sentence or two (no confidential details). Returns whether it is in scope, which service fits, what each suggested service covers (deliverables and turnaround), and the fixed fee for each (plus service_id, if you name one). Share the fee with your human before requesting an engagement. Legal information only, not legal advice.

    Annotations the server declares

    • title: Check scope and fee (free)
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • conflict_checkFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Free. Required before any product details are shared. Names only: the client company, the human principal, other people involved, and any adverse, competing, or counterparty companies. The attorney reviews every check.

    Annotations the server declares

    • title: Start a conflict check
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • feature_checkFor engaged clients, with the human's approval (it may be billed).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    For engaged clients, with the human's approval (it may be billed). Call before building a change that matches counsel-triggers.json. Do not ship the change until counsel responds.

    Annotations the server declares

    • title: Request a feature check (may be billed)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • request_engagementAfter conflict_check.No findings

    Why it is in this group

    • The name "request_engagement" says "request": a word for a change.
    Description, as the server wrote it
    After conflict_check. Send a short matter_summary so the attorney can decide whether to take the matter. Describe the product the way you would describe it publicly. Do not send code, secrets, user data, or confidential business plans. The attorney uses this summary only to decide whether the firm can and will take the matter, and keeps it confidential. No attorney-client relationship exists, and no legal advice is given, until the human principal signs the engagement letter. Returns a matter_id and a secret matter_token (shown once; store it securely). The attorney reviews conflicts and the summary, may ask a few scoping questions (see get_matter), and then accepts (possibly under a different service) or declines. If accepted, the engagement letter goes to the principal's email for signature. The fixed fee is due when the work is delivered. You cannot sign on the principal's behalf.

    Annotations the server declares

    • title: Ask the firm to take a matter
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • submit_intakeOnly after the engagement letter is signed.No findings

    Why it is in this group

    • The name "submit_intake" says "submit": a word for a change.
    Description, as the server wrote it
    Only after the engagement letter is signed. Product facts per https://mandatelaw.ai/api/intake-schema.json. Each fact has a value, a source (prefer verified_in_code), and evidence (paths and short excerpts; no secrets).

    Annotations the server declares

    • title: Submit product facts (after signing)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • get_counsel_triggersFree.No findings

    Why it is in this group

    • The name "get_counsel_triggers" says "get": a word for reading.
    Description, as the server wrote it
    Free. The template list of product changes that need legal review before shipping.

    Annotations the server declares

    • title: Get counsel triggers
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_matterStatus, counsel's open questions, feature checks, and deliverables (documents, privileged_memo, build_spec, verification_checklist, counsel_triggers).Reads private dataNo findings

    Why it is in this group

    • The name "get_matter" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "status" and "document": it reads documents.
    Description, as the server wrote it
    Status, counsel's open questions, feature checks, and deliverables (documents, privileged_memo, build_spec, verification_checklist, counsel_triggers). Privileged: follow the `privilege` block in the response, and commit only the parts listed in deliverable.handling.safe_to_commit.

    Annotations the server declares

    • title: Get matter status and deliverables
    • readOnlyHint: true
    • destructiveHint: false
    • 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 untrusted-input or outbound.

Reads private data1
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.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:20 UTC, unchanged since Nov 21, 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
7
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 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mandatelaw.ai/mcp: tools/list returned 9 tools to an anonymous client, including check_scope (write), conflict_check (write), request_engagement (write), submit_intake (write), answer_open_question (write) and 2 more

    What this check looks for

Posture changes

  1. Nov 21, 2026
    • Tools that change things, listed without credentials: 6 to 7

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 7.View diff
    • Tools that change things, listed without credentials: 6 to 7
  2. Tools1 added, 8 changed.+1 added~8 changedView diff
  3. Tools8 changed.~8 changedView diff

Install

Pinned to version 0.2.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http counsel https://mandatelaw.ai/mcp
claude mcp add --transport http counsel https://mandatelaw.ai/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__counsel__get_matter",
      "mcp__counsel__get_counsel_triggers"
    ],
    "ask": [
      "mcp__counsel__check_scope",
      "mcp__counsel__conflict_check",
      "mcp__counsel__request_engagement",
      "mcp__counsel__submit_intake",
      "mcp__counsel__answer_open_question",
      "mcp__counsel__feature_check",
      "mcp__counsel__check_change"
    ],
    "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 counsel. Review it before you use it.

Capability tags behind 1 rule
  • mcp__counsel__get_matter private-data

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/ai.mandatelaw/counsel/verify?hash=87a3efdafe8913f2b12b8909b1cfd925114a92f1a69a67a3bc78cd325ffad256" | jq -e '.changed == false'

Pinned hash 87a3efdafe89, from Nov 18, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.mandatelaw/counsel/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.mandatelaw/counsel
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.mandatelaw/counsel.svg)](https://radar.anlyon.com/servers/ai.mandatelaw/counsel)

Source: MCP Registry. Synced Nov 18, 2026, 18:17 UTC.

Mandate Law: legal counsel for AI products MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Mandate Law: legal counsel for AI products MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Mandate Law: legal counsel for AI products MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Mandate Law: legal counsel for AI products 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 Mandate Law: legal counsel for AI products MCP server have?

9 tools: 7 write, 2 read. check_scope, conflict_check, request_engagement, submit_intake, answer_open_question, feature_check, check_change, get_matter and 1 more.

Does the Mandate Law: legal counsel for AI products MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Mandate Law: legal counsel for AI products MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Mandate Law: legal counsel for AI products MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.