Skip to content
Official MCP RegistryListed

Mandate Law: legal counsel for AI products

Part ofMandate Law: legal counsel for AI productsMCP server

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

First seen 13 Nov 2026. Evidence as of 17 Nov 2026.

9
Tools
From an anonymous probe
1
Source listings
Each with its own history
40
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
answer_open_questionAnswer 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.Changes data
check_changeFree. 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.Read-only
check_scopeFree. 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.Read-only
conflict_checkFree. 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.Changes data
feature_checkFor 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.Changes data
get_counsel_triggersFree. The template list of product changes that need legal review before shipping.Read-only
get_matterStatus, 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.Read-only
request_engagementAfter 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.Changes data
submit_intakeOnly 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).Changes data

Change history

  1. request_engagement: input schema changed
  2. check_scope: input schema changed
  3. check_scope: description changed (+"what each suggested service covers (deliverables" +"turnaround), and" -"suggested service")
  4. check_change: tool added
  5. answer_open_question: input schema changed
  6. submit_intake: input schema changed
  7. submit_intake: annotations changed
  8. request_engagement: input schema changed
  9. request_engagement: annotations changed
  10. get_matter: input schema changed
  11. get_matter: annotations changed
  12. get_counsel_triggers: annotations changed
  13. feature_check: input schema changed
  14. feature_check: annotations changed
  15. conflict_check: input schema changed
  16. conflict_check: annotations changed
  17. check_scope: input schema changed
  18. check_scope: annotations changed
  19. answer_open_question: input schema changed
  20. answer_open_question: annotations changed
  21. submit_intake: title changed
  22. submit_intake: annotations changed
  23. request_engagement: title changed
  24. request_engagement: annotations changed
  25. get_matter: title changed
  26. get_matter: annotations changed
  27. get_counsel_triggers: title changed
  28. get_counsel_triggers: annotations changed
  29. feature_check: title changed
  30. feature_check: annotations changed
  31. conflict_check: title changed
  32. conflict_check: annotations changed
  33. check_scope: title changed
  34. check_scope: annotations changed
  35. answer_open_question: title changed
  36. answer_open_question: input schema changed
  37. answer_open_question: annotations changed
  38. Name changed from "Mandate Law" to "Mandate Law: legal counsel for AI products" (registry)
  39. Description changed (registry)
  40. Listed (registry)
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registryai.mandatelaw/counsel13 Nov 202617 Nov 20262
Mandate Law: legal counsel for AI products on Official MCP Registry | InvokeRank