UN Charter 1945
UN Charter (1945, as amended) as an executable model with worked cases; not UN-affiliated
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http un-charter-1945 'https://mcp.arxo.io/mcp/charter'
{
"mcpServers": {
"un-charter-1945": {
"type": "http",
"url": "https://mcp.arxo.io/mcp/charter"
}
}
}
@arxo/mcp-charterclaude mcp add un-charter-1945 -- npx -y @arxo/mcp-charter@0.1.8
{
"mcpServers": {
"un-charter-1945": {
"command": "npx",
"args": [
"-y",
"@arxo/mcp-charter@0.1.8"
]
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
arxo-charter-1945
Pinned canon, executable as it stands: source text with provenance, the
model built over it and the scenarios that check its answers. The norms
here are data — they are executed by law; this repository carries no
rule code of its own.
Contents
| Package | Version | Scenarios | Dependencies |
|---|---|---|---|
doctrine.iura_humana | 0.1.0 | 1 | 0 |
un.charter | 0.1.0 | 169 | 1 |
How it is verified
Every package is built by package.py with the pinned toolchain: compilation,
§267 scenarios on both evaluators, replay of saved evaluations and a rebuild
from the release itself. A failure of any step stops the build.
python3 tools/toolchain.py download --lock toolchain.lock.json --out /tmp/law-tools
python3 /tmp/law-tools/package.py packages/<name> \
--lawc /tmp/law-tools/law-cli --offline --out /tmp/<name>-release
Dependencies
Dependency bytes are pinned under packages/<name>/deps/ and verified against the contentHash recorded in law.lock: the build and the CI are offline.
Worked cases
Each collection is a case package of its own: the facts, the questions and
the answers, with the pinned canon as its dependency. Ask one from its
directory with law ask . — nothing is downloaded.
Rights
Code and model: see LICENSE. The pinned texts of the publishers keep their
own terms of reproduction, listed per package in NOTICE; those terms are
not covered by the code licence.
Maintainer: Rifat Dzhumagulov (hi@arxo.io). Address: https://github.com/arxohq/arxo-charter-1945.
Questions fréquentes
Qu'est-ce que UN Charter 1945 ?
UN Charter (1945, as amended) as an executable model with worked cases; not UN-affiliated
Comment installer UN Charter 1945 ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http un-charter-1945 'https://mcp.arxo.io/mcp/charter'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour UN Charter 1945 ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
UN Charter 1945 est-il open source ?
Oui. Son code est sur GitHub sous licence Apache-2.0.
Qui maintient UN Charter 1945 ?
Il est publié par arxohq. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.