io.arxo/charter

up checked 2026-11-11T04:37:22.271Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

UN Charter 1945

Publisher-provided description

UN Charter (1945, as amended) as an executable model with worked cases; not UN-affiliated

Summary by lookupd

Query, explain, and check formalised UN Charter provisions: search rules, run legal questions with proofs, and inspect editions and sources.

Install

Claude Code, remote (streamable-http)

claude mcp add --transport http charter https://mcp.arxo.io/mcp/charter

Claude Code, npm package (stdio)

claude mcp add charter -- npx -y @arxo/mcp-charter

Codex, remote (streamable-http)

codex mcp add charter --url https://mcp.arxo.io/mcp/charter

Codex, npm package (stdio)

codex mcp add charter -- npx -y @arxo/mcp-charter

Cursor, remote (streamable-http) → .cursor/mcp.json

{
  "mcpServers": {
    "charter": {
      "url": "https://mcp.arxo.io/mcp/charter"
    }
  }
}

Cursor, npm package (stdio) → .cursor/mcp.json

{
  "mcpServers": {
    "charter": {
      "command": "npx",
      "args": [
        "-y",
        "@arxo/mcp-charter"
      ]
    }
  }
}

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (21 tools)

Publisher-provided text

• law_search A semantic SEARCH over formalised law: a question or a notion in your own words → candidates with addresses — predicates with signatures, rules, article fragmen
• law_passport Passport of an exact release: purpose, interface, boundaries, checks and performance. The reports section holds the history of measurements, failures included.
• law_answer_capabilities A machine-readable matrix of the Lens producers that are actually installed, of replay/projection checks, profiles, limits and the contract tests that confirm t
• law_capture_answer Run a registered producer and obtain producerControl/0.2 for a later verifiable preparation of a Lens. The producer is chosen only from the shipped registry.
• law_prepare_answer At the explicit request of the user, repeat between 1 and 12 earlier law_ask or law_process_run calls, compare their replayControl strictly, and prepare a non-p
• law_publish_answer Publish a prepared document. Repeating it with the same preparationId idempotently returns the same URL and the same separate revocation secret.
• law_revoke_answer Revoke a published document using its separate secret. The public id alone grants no control; revocation closes the HTML page, the API and the download.
• law_packages The catalogue of formalised law: instruments, predicates with signatures, the boundaries of coverage. This is where the NAMES of predicates come from — they mus
• law_ask Put a question to formalised law. When the answer is "not established" it carries whyNot — the engine's why_not report: the candidate rules and the state of eve
• law_screen Build a necessary condition — a superset — for the preliminary selection of rows from an external source. This is NOT a legal answer and NOT SQL: the result is
• law_rules The rules of formalised law put into words: exactly how a predicate is derived (premises, source articles). Call this BEFORE supplying facts to law_ask — the ru
• law_explain Unfold the proof of a law_ask answer into a chain "rule ← premises → conclusion". The compact input: question (the original law_ask arguments, truth/collect), r
• law_inspect Evaluation inspector over a SAVED evaluation document: summary — the origin card, resultHash and snapshot verification, listings of results, positions and issue
• law_case_ask The ask operation: run a registered case of a case package over its pinned dependencies and return the answer: by default a projection of the evaluation documen
• law_sources Sources: by default short excerpts (view=summary), 5 texts per page, with the address of the full text in fragments[].full. Either package or fragment is requir
• law_argue How robust a conclusion is: the map of the dispute under the argumentation profile The answer falls into four classes: SKEPTICALLY_ACCEPTED — the conclusion is
• law_process Which stages the procedure established by an instrument consists of, and whether it carries a structural defect. The stages, the transitions and the condition o
• law_process_run How a particular case will run, step by step: a log of {date, attempt?, facts?} is executed frame by frame, and the law of each frame is the law of ITS date. Th
• law_editions The axis of editions (O-2): what changed in an instrument between two dates of the law — the state of the editions, the dating of the norms and the semantic dif
• law_query A deterministic LawQL query over the CLIR of a formalization: a question about the model of the act itself, not about a case. Relations (14): anchors, edges, fi
• law_report A REPORT of a divergence between the formalisation and the source: the answer contradicts the pinned text, a norm of the source is not expressed by a rule, a la

Details

• Version: 0.1.8
• Transports: streamable-http, stdio
• Uptime (7 days): 100%
• Median latency: 919 ms
• First indexed: 2026-11-01T09:02:53.326Z
• Last seen in registry: 2026-11-01T09:02:53.336Z
• Repository: https://github.com/arxohq/arxo-charter-1945
• Website: https://charter.law.arxo.io/

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/io.arxo/charter.svg)](https://lookupd.com/servers/io.arxo/charter)

• 62092 servers
• Last crawl: 2026-11-11T17:38:11.606Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp