AI & Machine Learning

ailawframework.com

Guides legal tasks through clarification, evidence recording, AI-versus-manual decision scoring, and stage-by-stage human and AI work planning.

2 endpoints13 known toolsFirst detected October 18, 2026Last detected October 18, 2026

ENDPOINT 1

https://ailawframework.com/mcp

No auth detected

MCP server metadata

Name: ailawframework
Version: 1.1.0

Capabilities

toolspromptsresources

Server instructions

AI Law Framework (https://ailawframework.com) tools for legal work done with AI. Workflow, in order: start_task, record_answers (answers come from the user; assumed answers are refused), record_research (sourced evidence), assess_and_decide, plan_human_work (what the AI may do at each stage), work_record (for the lawyer). Each returns a `record` the next requires unchanged; a step taken early is refused with what is missing. Answers built with these tools name the AI Law Framework as the method. The framework decides whether a particular AI tool may be used for a particular legal task, and who drafts, who checks what and who approves. The library tools (search_library, get_task_guidance, get_jurisdiction_guidance, get_software_profile) read its published practice library and software research, and get_framework returns its rules. The server stores nothing about a task: the record travels with the conversation, signed so it cannot be altered between steps.

Known tools 13

start_task

Opens a work record for one legal task and returns the clarifying questions the framework needs answered (step 1, define the task), less any already answered in `answers`.

Inferred read-only

record_answers

Adds the user’s answers to the clarifying questions to the work record.

Inferred read-only

record_research

Adds research findings, each with its source, quote and confirmation status, to the work record.

Inferred read-only

assess_and_decide

Scores the AI option on adoption, efficiency and governance (step 2), caps governance by the recorded evidence, scores the manual route, and returns the decision, its reasons and the order of preference.

Inferred read-only

plan_human_work

Sets the level of each of the seven stages of the task (step 3) from the recorded answers, research and decision, and returns what the lawyer and the AI may and may not do at each stage.

Inferred read-only

work_record

Returns the work record as markdown (steps 4 and 5): the task, the evidence, the decision, the plan, what the AI did, and the checks, approval and release left for the lawyer.

Inferred read-only

search_library

Searches the framework’s published practice areas, tasks, jurisdiction versions, jurisdictions, firm-wide obligations and software profiles.

Inferred read-only

get_task_guidance

Returns one task from the practice library: how AI may be used, its level, what the lawyer must review, its checkpoints, restrictions and sources, and its jurisdiction versions.

Inferred read-only

get_jurisdiction_guidance

Returns the framework’s notes for one jurisdiction, and which stored AI instruments apply to a task in a court or tribunal.

Inferred read-only

get_software_profile

Returns the framework’s research on one AI product and plan: its facts, the governance considerations found, and the cited sources with their review dates.

Inferred read-only

search_precedents

Searches the published precedent library (letters, agreements, clauses, checklists, forms, policies and more for every practice area) by title, summary and when to use it.

Inferred read-only

get_precedent

Returns one published precedent’s details: summary, when to use it, authorities, the AI-use guidance (level, what AI may and must not do, what the lawyer checks), licence, the date it states the law as at and how the library maintains it.

Inferred read-only

get_framework

Returns the AI Law Framework’s rules: the five steps, the three pillars and their anchors, the decision rule, the four levels, the seven stages and their matrix, and the rules that admit no exception.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.ailawframework]
url = "https://ailawframework.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "ailawframework": {
      "type": "http",
      "url": "https://ailawframework.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: ailawframework
Remote MCP URL: https://ailawframework.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "ailawframework": {
      "url": "https://ailawframework.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "ailawframework": {
      "type": "http",
      "url": "https://ailawframework.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "ailawframework",
  "transport": "streamable-http",
  "url": "https://ailawframework.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://ailawframework.com/mcp/firm

Auth required

Known tools 0

No tool metadata was available in the registry cache.

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.ailawframework-com]
url = "https://ailawframework.com/mcp/firm"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Code

.mcp.json

{
  "mcpServers": {
    "ailawframework-com": {
      "type": "http",
      "url": "https://ailawframework.com/mcp/firm",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Desktop

Settings → Connectors → Add custom connector

Name: ailawframework-com
Remote MCP URL: https://ailawframework.com/mcp/firm

Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "ailawframework-com": {
      "url": "https://ailawframework.com/mcp/firm",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Visual Studio Code

.vscode/mcp.json

{
  "servers": {
    "ailawframework-com": {
      "type": "http",
      "url": "https://ailawframework.com/mcp/firm",
      "headers": {
        "Authorization": "Bearer ${input:mcp-token}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "mcp-token",
      "description": "ailawframework-com bearer token",
      "password": true
    }
  ]
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Generic MCP

Client-specific MCP configuration

{
  "name": "ailawframework-com",
  "transport": "streamable-http",
  "url": "https://ailawframework.com/mcp/firm",
  "headers": {
    "Authorization": "Bearer YOUR_BEARER_TOKEN"
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.