io.github.xenarch-ai/xenarch-mcp

It requires XENARCH_PRIVATE_KEY, XENARCH_RPC_URL, XENARCH_NETWORK, and XENARCH_MAX_PAYMENT_USD. The private key is highly sensitive and can directly control on-chain payments; leakage or an overly high payment cap could lead to financial loss. The other variables are mainly network and limit configuration, which is typical for this kind of payment tool.

No fixed remote host is listed in the objective materials, but the presence of XENARCH_RPC_URL indicates the tool will likely make network requests to a user-configured blockchain RPC endpoint. The available documentation does not state what user data is sent where, so normal configured network egress is expected, but there is no clear red flag of sending data to unrelated or unknown endpoints.

The system marks it as executes-code, indicating normal MCP capability to run a local service/code. Based on the provided materials, there is no evidence that it requests elevated system privileges unrelated to its payment function, nor any suspicious command-execution behavior, so this remains a caution-level characteristic of the tool class.

No README is provided, so the exact scope of file, wallet-state, or transaction-record access cannot be confirmed. As a locally run payment-oriented MCP, it will at minimum access environment-based private key and network settings and process payment-related data. There is currently no clear sign that it requests unrelated directory browsing, bulk local file reads, or excessive data permissions.

The source is an official registry entry with an auditable open-source repository and recent updates within the last year; these are positive factors that reduce risk. Although no license is declared and community stars are low, limiting maturity signals, the available objective evidence shows no closed-source, abandoned, or otherwise clearly suspicious supply-chain red flags.