io.github.xenarch-ai/xenarch-mcp
NPM · @XENARCH/AGENT-MCP · SCANNED SEP 20
Xenarch — x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via @xenarch/core > x402-fetch > x402 > wagmi > @wagmi/connectors > @metamask/sdk > uuid. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 400 of 527 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 74 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 7663 tokens (~73/item across 104 items; 103 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 14 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 104 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.xenarch-ai/xenarch-mcp server?
io.github.xenarch-ai/xenarch-mcp runs locally as an npm package, launched with npx -y @xenarch/agent-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @xenarch/agent-mcp
claude mcp add xenarch-ai-xenarch-mcp -- npx -y @xenarch/agent-mcp
{
"mcpServers": {
"xenarch-ai-xenarch-mcp": {
"command": "npx",
"args": [
"-y",
"@xenarch/agent-mcp"
]
}
}
} {
"servers": {
"xenarch-ai-xenarch-mcp": {
"command": "npx",
"args": [
"-y",
"@xenarch/agent-mcp"
]
}
}
} codex mcp add xenarch-ai-xenarch-mcp -- npx -y @xenarch/agent-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xenarch-ai-xenarch-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@xenarch/agent-mcp"
],
"enabled": true
}
}
} openclaw mcp add xenarch-ai-xenarch-mcp --command npx --arg -y --arg @xenarch/agent-mcp
mcp_servers:
xenarch-ai-xenarch-mcp:
command: "npx"
args: ["-y", "@xenarch/agent-mcp"] {
"McpServers": {
"xenarch-ai-xenarch-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@xenarch/agent-mcp"
]
}
}
} assistant mcp add xenarch-ai-xenarch-mcp -t stdio -c npx -a -y @xenarch/agent-mcp
{
"mcpServers": {
"xenarch-ai-xenarch-mcp": {
"command": "npx",
"args": [
"-y",
"@xenarch/agent-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −2
- Stability: pass → 0.83 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.90 → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 0
- CVE-2026-67316 no longer affects this package ▲ security
- CVE-2026-67313 no longer affects this package ▲ security
- CVE-2026-67312 no longer affects this package ▲ security
- CVE-2026-67321 no longer affects this package ▲ security
- CVE-2026-67315 no longer affects this package ▲ security
- CVE-2026-67320 no longer affects this package ▲ security
- CVE-2026-67317 no longer affects this package ▲ security
- CVE-2026-67318 no longer affects this package ▲ security
- CVE-2026-67319 no longer affects this package ▲ security
- CVE-2026-67314 no longer affects this package ▲ security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@xenarch/agent-mcp@1.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-vcc3-ghjq-m6fr | CVE-2026-45822 | medium | yes | |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-58qx-3vcg-4xpx | CVE-2026-45736 | medium | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-96hv-2xvq-fx4p | CVE-2026-48779 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 400 packages
| Packages resolved | 400 |
|---|---|
| Deprecated | 13 |
| Stale | 102 |
| No linked repository | 2 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
xenarch_verify_account_email ~33
Verify the account email with the emailed code.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The verification code from the email. |
No output schema declared.
No examples provided.
xenarch_verify_domain ~47
Verify the merchant's domain via its DNS TXT record at _xenarch.<merchant_site> (XEN-394). Set merchant_site first via xenarch_update_merchant_profile.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
xenarch_wallet_status ~76
Show the agent's local payment wallet: its address, USDC balance on Base, and whether it's funded. Use this to find the address the user needs to top up with USDC, or to check the balance before paying. This is the wallet that signs payments — separate from the wallet used to sign in to the dashboard.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.xenarch-ai/xenarch-mcp server?
io.github.xenarch-ai/xenarch-mcp is listed in the public MCP registry as io.github.xenarch-ai/xenarch-mcp. Xenarch, x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2. This page covers its npm package (@xenarch/agent-mcp).
Is the io.github.xenarch-ai/xenarch-mcp server safe to use?
io.github.xenarch-ai/xenarch-mcp scores 81 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.xenarch-ai/xenarch-mcp server expose?
io.github.xenarch-ai/xenarch-mcp exposes 103 tools: xenarch_check_gate, xenarch_pay, xenarch_wallet_status, xenarch_get_history, xenarch_agent_login, and 98 more. Their descriptions and schemas cost roughly 7,640 tokens of context every time the server is loaded.
Is the io.github.xenarch-ai/xenarch-mcp server still maintained?
io.github.xenarch-ai/xenarch-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.xenarch-ai/xenarch-mcp server under?
io.github.xenarch-ai/xenarch-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.