Skip to content

MCP servers › io.arxo › charter

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.arxo/charter

UN Charter (1945, as amended) as an executable model with worked cases; not UN-affiliated — the publisher's description

7 of 9 record checks metRead-only · tools listed 2026-10-23Topic: data-and-databases · AI-classifiedPricing: open-source · AI-classifiedversion 0.1.8PythonApache-2.0standard input/output, streamable HTTP20 tools

Summary

io.arxo/charter is a remote and local MCP server listed in the official MCP registry at version 0.1.8. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 20 tools, 0 resources and 0 prompts.

Record checks

7 of 9 record checks met

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not met: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • #1,863 of 15,112 packages by monthly downloads, tied with 1 other
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote and local package
Transport
standard input/output, streamable HTTP
Sign-in
none needed to open a session
Package
npm · listed version current
License
Apache-2.0
Dependencies
no known high or critical advisories
Repository
public
Tools
20
Described as changing data
5 of 20 toolsAI-classified
Topic
data-and-databasesAI-classified
Pricing
open-sourceAI-classified
Last tested
2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (law_revoke_answer). That is our reading of the names; we did not call it. Source: our connection, 2026-10-23.

Worth knowing before you connect it

  • 5 tools are described as changing something (law_capture_answer, law_prepare_answer, law_publish_answer, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
0.1.8, published 2026-10-14 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-14 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-10-14; 2 in the 90 days before the 2026-10-23 snapshot.
Most recent 2 versions
  • 0.1.8 · 2026-10-14
  • 0.1.7 · 2026-10-14
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-22
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.1.8 (published 2026-10-14).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
20tools
0resources
0prompts

5 of 20 tools are described as changing something (creating, editing, deleting, sending or running). For 2 the reading was uncertain, so no mark is shown.

  • law_searchon 6 other serversreads or searches

    “A semantic SEARCH over formalised law: a question or a notion in your own words → candidates with addresses — predicates with signatures, rules, article fragments.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    4 inputs, 1 required
    • kindsarray“narrow the kinds of candidate”
    • limitinteger“how many candidates (8, at most 25)”
    • packagestring“search inside this instrument only”
    • querystringrequired“a question or a notion in your own words”
  • law_passporton 5 other serversreads or searches

    “Passport of an exact release: purpose, interface, boundaries, checks and performance.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    6 inputs, 3 required
    • contentHashstringrequired
    • limitinteger
    • namestringrequired
    • offsetinteger
    • sectionsarray
    • versionstringrequired
  • law_answer_capabilitieson 5 other serversreads or searches

    “A machine-readable matrix of the Lens producers that are actually installed, of replay/projection checks, profiles, limits and the contract tests that confirm them.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    Takes no inputs.

  • law_capture_answeron 5 other serversruns code or commandsdescribed as changing data

    “Run a registered producer and obtain producerControl/0.2 for a later verifiable preparation of a Lens.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    2 inputs, 2 required
    • producerstringrequired
    • requestobjectrequired
  • law_prepare_answeron 5 other serversdescribed as changing data

    “At the explicit request of the user, repeat between 1 and 12 earlier law_ask or law_process_run calls (the course of a case, DECISION-0160), compare their replayControl strictly, and prepare a non-pu…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    6 inputs, 1 required
    • assistantobject
    • calculationsarray
    • documentVersionenum“Version of the immutable document; 0.1 is kept for transitional compatibility, 0.2 includes all native results and the common reader.”
    • languageenum
    • producerRunsarray“Runs of registered producers with control/0.2; mutually exclusive with calculations.”
    • questionstringrequired
  • law_publish_answeron 5 other serverscreates or changes datadescribed as changing data

    “Publish a prepared document.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • preparationIdstringrequired
  • law_revoke_answeron 5 other serversdeletesdescribed as changing data

    “Revoke a published document using its separate secret.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    2 inputs, 2 required
    • publicIdstringrequired
    • revokeSecretstringrequired
  • law_packageson 5 other serversreads or searches

    “The catalogue of formalised law: instruments, predicates with signatures, the boundaries of coverage.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    6 inputs
    • catalogstring“together with package: page the catalogue of questions, the norms, the constants or the task guides of the instrument instead of its signatures; "task-guides" …”
    • guidestring“together with catalog="task-guides": the detail of one guide — a name <package>/<id> (as in prompts/list) or an id together with package”
    • limitinteger“how many per page: instruments (overview 20, query 20), signatures of an instrument (20, at most 300) or elements of a catalog list (questions 20, norms 20, co…”
    • offsetinteger“from which element of the page (0); the unit is the pageUnit of the answer”
    • packagestring“the full signatures of this instrument”
    • querystring“a substring filter over signatures, labels and constants (case-insensitive)”
  • “Put a question to formalised law.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    21 inputs
    • afterstring“deadline: the date of the event”
    • afterTimestring“deadline: the time of filing”
    • argsarray“the arguments of the predicate in the order of its signature; with kind='collect' exactly one of them is the selection variable ?name (for example ['urn:x:wate…”
    • calc“kind='calc': a tree {op,left,right}, op ∈ add|sub|mul|div|le|lt|ge|gt|eq|ne (the synonyms divide/multiply/plus/minus and the signs are accepted); the leaves ar…”
    • cutoffstring“deadline: the hour operations close”
    • daysinteger“deadline: the length of the period”
    • deadlinePolicyobject“the §86 policy for counting time limits expressed in days: {start_count: 'same_day'|'next_day', include_end: true|false, roll: 'no_roll'|'next_working_day'|'pr…”
    • evidencearray“case documents, section 74, evidence_item nodes.”
    • evidencePolicystring“StableId of an evidence_policy node, section 78.2.”
    • factsarray“facts of the case: [{predicate, args, negated?, package?, provenance?, judgment?}].”
    • focusedboolean“kind='truth': ask as focused_truth (§181.3) — the same answer as the full truth, but the proof and the warnings cover only the cone of the question; the answer…”
    • kindenum“the kind of question (truth by default)”
    • legalTimestring“the date of the law (YYYY-MM-DD)”
    • packagestring“narrow the question to one package of law”
    • predicatestring“what is being asked, e.g.”
    • proofboolean“return the evaluation field with the proof graph in the answer — a ready-made input for law_explain (kind truth|collect; by default a summary without the graph)”
    • responseModeenum“full (default) — the complete answer.”
    • selectedInterpretationsarray“named readings §152; for an exactly_one group choose exactly one StableId out of law_packages/law_rules”
    • supportEdgesarray“support edges, section 75, support_edge nodes: from is the document id, to is the fact literal, relation is supports or refutes.”
    • unitenum
    • versionstring“the exact package version pinned by the client (open('name@version')); if it differs from the profile composition the host refuses instead of answering with an…”
  • “Build a necessary condition — a superset — for the preliminary selection of rows from an external source (DECISION-0120).”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    5 inputs, 4 required
    • bindingobjectrequired“a law.screen.binding/0.1 artefact”
    • goalstringrequired“a StableId or a unique short name of the goal”
    • legalTimestring“the date of the law YYYY-MM-DD; without it every window of every rule is taken into account”
    • packagestringrequired“the package key from law_packages”
    • sourceSchemaContentHashstringrequired“the actual sha256 of the source schema”
  • law_ruleson 5 other serversreads or searches

    “The rules of formalised law put into words: exactly how a predicate is derived (premises, source articles).”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    5 inputs
    • langenum“the language the rules are put into (DECISION-0032; the language of the profile by default; the rest are draft packs, with §218 label overlays)”
    • limitinteger“package: how many rules per page (20; the budget may lower it)”
    • offsetinteger“package: from which rule (0)”
    • packagestring“every rule of the instrument”
    • predicatestring“the rules that derive this predicate”
  • law_explainon 5 other serversreads or searches

    “Unfold the proof of a law_ask answer into a chain "rule ← premises → conclusion".”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    6 inputs
    • answerResourcestring“the fullAnswer.uri of a stored answer taken with proof=true”
    • codeHashstring
    • evaluationobject“the evaluation document from law_ask”
    • nodeIdstring
    • questionobject“the original law_ask arguments”
    • resultHashstring
Show 8 more tools
  • law_case_askon 5 other serversruns code or commands

    “The ask operation §168.4 (DECISION-0165, DECISION-0399): run a registered case of a case package over its pinned dependencies and return the canonical evaluation document with a proof and a manifest.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    7 inputs, 1 required
    • argsobject“the card parameters: name → string expression of the language”
    • cardstring“the id of a card of an installed catalog DECISION-0190”
    • casestring“the name of the case declaration from [[cases]]; optional when there is only one case”
    • evaluatestring“the string `evaluate <expression>;` §267.2; requires queryId”
    • packagestringrequired“the path to the case package (the directory holding law.toml) from the root of the repository”
    • queryobject“the question as JSON per query.schema.json; queryId is a URN in the namespace of the package, or a short name given in queryId”
    • queryIdstring“without query/evaluate — the choice of a saved queries/*.json by short name or full URN; with evaluate — the id of the question being run”
  • law_sourceson 5 other serversreads or searches

    “Sources: by default short excerpts (view=summary), 5 texts per page, with the address of the full text in fragments[].full.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    10 inputs
    • contentHashstring“the hash of the full text taken from the previous part”
    • fragmentstring“the StableId of a fragment”
    • languagestring“the language of the variant, as given on the source card”
    • limitinteger“how many texts: summary 5, full 1 (the budget may lower it)”
    • offsetinteger“from which fragment (0)”
    • packagestring“the package key — every fragment of that instrument”
    • statusstring“the status of the variant, as given on the source card”
    • textLimitinteger“the maximum number of Unicode characters in a part of the text (also ≤8000 bytes of UTF-8)”
    • textOffsetinteger
    • viewenum
  • “How robust a conclusion is: the map of the dispute under the argumentation profile §274 (DECISION-0039).”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    6 inputs, 1 required
    • argsarray“the arguments of the predicate”
    • factsarray“facts of the case: [{predicate, args, negated?, provenance?}].”
    • legalTimestring“the date of the law (YYYY-MM-DD)”
    • limitsobject“the caps of the §274 profile: maxArguments (64), maxExtensions (8), maxUndecided (16)”
    • packagestring“narrow the question to one package of law”
    • predicatestringrequired“the conclusion whose robustness is being measured”
  • law_processon 3 other serversreads or searches

    “Which stages the procedure established by an instrument consists of, and whether it carries a structural defect (O-5, DECISION-0052).”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    1 input
    • packagestring“the instrument; without it — the list of instruments that carry procedures”
  • law_process_runon 3 other serversruns code or commands

    “How a particular case will run, step by step (O-5, DECISION-0052): a log of {date, attempt?, facts?} is executed frame by frame, and the law of each frame is the law of ITS date.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    6 inputs, 3 required
    • instancestringrequired“what is going through the procedure: the number of the lot, of the application, of the case”
    • legalTimestring“the base date (YYYY-MM-DD); the date of a frame is set by the step itself”
    • packagestringrequired“the instrument”
    • probeTimestring“the instant of a hypothetical attempt, used to work out the steps available on the last frame; without it the available steps are not computed — the tool does …”
    • procedurestring“the procedure, where there is more than one”
    • stepsarrayrequired“the log of the case: [{date, attempt?, time?, decisionTime?, knowledgeTime?, facts: [{predicate, args}]}]; on an attempted transition `time` is the instant of …”
  • law_editionson 3 other serversreads or searches

    “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 diff §215 between the D1 projections.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    3 inputs, 3 required
    • dateAstringrequired“the date of the law "before" (YYYY-MM-DD)”
    • dateBstringrequired“the date of the law "after" (YYYY-MM-DD)”
    • packagestringrequired“the instrument of the corpus”
  • law_queryon 5 other serversruns code or commands

    “A deterministic LawQL query over the CLIR of a formalization: a question about the model of the act itself, not about a case.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    11 inputs
    • argumentsobject“the question parameters: an object of name → string (predicate, node, type — URNs; pkg — a package.name or a glob)”
    • caseobject“the case for query-over; it replaces the case clause”
    • corpusstring“the snapshot scope: a package.name (for example kz.corpus.labour_code) or a glob over package.name; without corpus, the whole profile slice”
    • engineenum“there is one engine — the core; the reference implementation is called by its own command”
    • fullboolean“return the full queryResult instead of a page; only when the scope is one package”
    • limitinteger“an explicit cap on eval() materialisations (it does NOT bound the rows — see rowLimit)”
    • querystring“inline LawQL”
    • questionstring“the name of a question from the corpus/ql/questions catalog (producers, readers, anchors-of, imports-of, links-of, type-step) or of a lint; instead of query”
    • rowLimitinteger“how many rows in structuredContent (20; the budget may lower it)”
    • rowOffsetinteger“from which row (0); continuation comes from next together with snapshot; structural queries only”
    • snapshotstring“the snapshot hash from next.snapshot of the previous page: a continuation on another snapshot is refused (SNAPSHOT_CHANGED)”
  • law_reporton 3 other serverscreates or changes datadescribed as changing data

    “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 §218 label diverges from the text, an add…”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    7 inputs, 4 required
    • callIdstring“the X-Law-Call-Id of the answer you disagree with”
    • categoryenumrequired“the kind of divergence: norm not expressed / outcome against the text / label against the text / address not found / text against the official one / other”
    • expectedstringrequired“what the source says (with the article)”
    • fragmentstring“the StableId of the source fragment”
    • observedstringrequired“what the system answered”
    • packagestringrequired“the instrument of the corpus”
    • predicatestring“the predicate the report is about”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 20 tools
Says what it returns
95% of 19 tools
States limits, defaults or errors
40% of 20 tools
Says when to use it
100% of 5 tools
Items covered per tool
3.3 of 4 on average

Counted from the listing

Parameters with a description
82% of 115
Tools with a description
100% of 20
Typical description length
704 characters

The tool set

Counted from the listing

Tools
20
Size of the list
about 9,825 tokens for an agent to load (characters ÷ 4)
Naming
20 of 20 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 20 of 20 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package @arxo/mcp-charter

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "charter": {
      "command": "npx",
      "args": [
        "-y",
        "@arxo/mcp-charter@0.1.8"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "charter": {
      "command": "npx",
      "args": [
        "-y",
        "@arxo/mcp-charter@0.1.8"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "charter": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@arxo/mcp-charter@0.1.8"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"charter","type":"stdio","command":"npx","args":["-y","@arxo/mcp-charter@0.1.8"]}'
Claude Code
claude mcp add --transport stdio charter -- npx -y @arxo/mcp-charter@0.1.8
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @arxo/mcp-charter@0.1.8
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.arxo.io/mcp/charter
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "charter": {
      "url": "https://mcp.arxo.io/mcp/charter"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "charter": {
      "type": "http",
      "url": "https://mcp.arxo.io/mcp/charter"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"charter","type":"http","url":"https://mcp.arxo.io/mcp/charter"}'
Claude Code
claude mcp add --transport http charter https://mcp.arxo.io/mcp/charter
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.arxo.io/mcp/charter --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.1.8
Latest stable
0.1.8
Status
current
Withdrawn
no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha512-n+dKQFyf3iSLNs2Cv…
Signature
signed
License
Apache-2.0

Source: the package registry · 2026-10-22.

Usage

Downloads
1,368 in the last month

Source: api.npmjs.org · 2026-10-22.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.arxo.io/mcp/charterSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23
Version 0.1.8 on npmExists and can be installedmatchesnpm · 2026-10-23
Repository github.com/arxohq/arxo-charter-1945Opens publiclymatchesapi.github.com · 2026-10-22

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.arxo · 6 servers
GitHub owner
an organization (arxohq)
Build record
signed
Repository
github.com/arxohq/arxo-charter-1945
Stars
0
Repository age
31–90 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-22; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Same tools as other registry entries

Tool lists read · names compared

Its 20 tools have exactly the same names as the tools of 3 other registry entries (all published under the same registry namespace). Their tool descriptions differ in places.

This can be one publisher's family of servers or one template reused under many names. It is a fact about the published tool lists, not a judgement of the publisher and not a safety finding; we compared tool names, not code.

Shared tool names (12 of 20 shown):

law_answer_capabilitieslaw_arguelaw_asklaw_capture_answerlaw_case_asklaw_editionslaw_explainlaw_packageslaw_passportlaw_prepare_answerlaw_processlaw_process_run

The other entries

All groups of servers with identical tool lists

Source: our read-only reads of each server's tool list · 2026-10-23. No tool was called.

Choosing

Record checks

Public records · not a safety rating

7 of 9 record checks met

  • #1,863 of 15,112 packages by monthly downloads, tied with 1 other
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
  • MetPackage names its licence with a standard (SPDX) identifierApache-2.0
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.arxo/charter

Answered from the data above

Is io.arxo/charter safe to install?

We do not rate servers as safe or unsafe. 7 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 5 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is io.arxo/charter free to use?

Its website (charter.law.arxo.io/) describes a open-source pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Does io.arxo/charter need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.arxo/charter been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can io.arxo/charter do?

It lists 20 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete and run code or commands. We did not call any tool, so this describes the text, not the behaviour.

Can io.arxo/charter change or delete data?

5 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.arxo/charter publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 0.1.8, the latest stable release on npm.

Where is the source code of io.arxo/charter?

In github.com/arxohq/arxo-charter-1945, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “data-and-databases” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,166 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 20 tools, 0 resources, 0 prompts.
  4. 4,304 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
open-source
read from charter.law.arxo.io/ · 2026-10-23

“Open source.”

Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
prompts, tools
our test · 2026-10-23
Transport
standard input/output, streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
registry · 2026-10-23
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
package registry · 2026-10-22
Integrity hash
declared (sri)
package registry · 2026-10-22
Signature / provenance
signed
package registry · 2026-10-22
Dependency advisories
none known
npm audit · 2026-10-23
Popularity
1,368 downloads a month
package registry · 2026-10-22
Publisher signals
owner: an organization · repository age: 31–90 days · stars: 0–9 · build record: signed
api.github.com · 2026-10-22
Maintenance
api.github.com · 2026-10-22
Environment
either (remote or your machine)
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.arxo/charter: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.arxo/charter

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 7 of 9 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.arxo/charter)](https://protocolprobe.com/mcp/servers/io.arxo/charter)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology