XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP
NPM · XPAYR-MCP · 2 COMPONENTS
21 MCP tools for non-custodial crypto checkout, USDT/USDC links, webhooks, and AI agents.
Available components
Last scanned (14 hours ago)
Scores higher than 53% of npm servers
Category Crypto and Web3
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1978 tokens (~89/item across 22 items; 21 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "xpayr_send_test_webhook" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 22 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 70
First indexed and scored.
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 21 Nov 2026 · Analysed npm/xpayr-mcp@1.0.0
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 →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
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 →
xpayr_apply_payment_coupon ~59
Validate and apply a merchant discount coupon code to an active pending payment session and recalculate the effective crypto price.
| Name | Type | Req | Description |
|---|---|---|---|
| coupon_code | string | yes | Discount coupon code to apply. |
| session_id | string | yes | Target payment session ID. |
No output schema declared.
No examples provided.
xpayr_approve_agent_intent ~65
Approve a pending AI agent payment intent from the merchant human-in-the-loop approval queue and optionally bridge it to a checkout session.
| Name | Type | Req | Description |
|---|---|---|---|
| intent_id | string | yes | Pending agent intent ID to approve. |
| note | string | – | Optional reviewer approval note. |
No output schema declared.
No examples provided.
xpayr_bridge_agent_intent_to_checkout ~53
Bridge an approved AI agent payment intent into a live executable XPayr payment session with hosted checkout URL and on-chain verification.
| Name | Type | Req | Description |
|---|---|---|---|
| intent_id | string | yes | Approved agent payment intent ID. |
No output schema declared.
No examples provided.
xpayr_calculate_gateway_fee_and_split ~178
Deterministically calculate XPayr flat 0.5% (50 bps) gateway fee split, net merchant wallet settlement, exchange withdrawal underpayment tolerance (1%, max $0.50), and cost savings compared to BitPay (1%), Coinbase Commerce (1%), NOWPayments (0.5%-1%), and Stripe (2.9% + $0.30). Works offline without API keys.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Transaction or monthly volume amount in USD/USDT (e.g., 1000.00). |
| currency | string | – | Settlement token symbol (e.g., USDT, USDC). |
| network | string | – | Blockchain network (e.g., tron-mainnet, solana-mainnet, bsc-mainnet, base-mainnet, arc-mainnet). |
No output schema declared.
No examples provided.
xpayr_create_ai_agent ~77
Provision a new merchant-managed AI commerce agent identity with scoped credentials and programmable spending guardrails.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Purpose and operational scope of the AI agent. |
| name | string | yes | Human-readable AI agent name (e.g., Procurement Bot Alpha). |
| wallet_address | string | – | Optional agent execution wallet address. |
No output schema declared.
No examples provided.
xpayr_create_payment_session ~388
Create a non-custodial crypto payment session supporting Dual Checkout (Web3 1-Click Pay & Direct Transfer / QR from Binance/Bybit/OKX with on-chain explorer verification), multi-chain agnostic links, 1-year reusable payment links, and automated HTML invoice email delivery.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Invoice amount in fiat/token units (e.g., 49.90). |
| cancel_url | string | – | HTTPS redirect URL if customer cancels checkout. |
| coupon_code | string | – | Optional promotional discount coupon code to apply. |
| currency | string | yes | Payment token symbol (e.g., USDT, USDC, SOL, TRX, BNB, ETH, MATIC). |
| customer_email | string | – | Buyer email address for invoice delivery and payment receipt notifications. |
| description | string | – | Human-readable order description shown on checkout and invoice. |
| ipn_callback_url | string | – | HTTPS webhook endpoint URL for HMAC-SHA256 signed payment lifecycle events. |
| is_multi_chain | boolean | – | When true, generates a universal multi-chain link allowing the buyer to dynamically choose their network and token at checkout. |
| is_reusable | boolean | – | When true, the payment link remains active for 1 year and accepts repeated payments. |
| network | string | – | Blockchain network key (e.g., tron-mainnet, bsc-mainnet, solana-mainnet, polygon-mainnet, base-mainnet, arc-mainnet, bsc-testnet). Optional if is_multi_chain is true. |
| order_id | string | – | Merchant internal order or invoice reference ID (e.g., ORD-1001). |
| send_invoice_email | boolean | – | When true and customer_email is provided, sends a branded responsive HTML invoice email with 1-click payment CTA. |
| success_url | string | – | HTTPS redirect URL after confirmed payment. |
No output schema declared.
No examples provided.
xpayr_get_merchant_balance ~41
Query confirmed non-custodial settlement volume, transaction counts, total merchant received amounts, and platform fees grouped by currency and blockchain network.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
xpayr_get_merchant_profile ~50
Retrieve authenticated merchant profile, business name, primary settlement wallet address, commission rate in basis points (50 bps = 0.5%), active API keys, and livemode status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
xpayr_get_payment_session ~81
Retrieve full details, metadata, settlement split amounts, checkout mode, and on-chain transaction hash for a specific XPayr payment session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Payment session ID (e.g., ps_6b5b7d8737c0e0ec0a04a29a045d2d5d). |
No output schema declared.
No examples provided.
xpayr_get_public_payment_status ~90
Poll real-time public checkout status, on-chain tx_hash, sender wallet address, block confirmations, and paid_at timestamp for any session (public endpoint, no API key required).
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Payment session ID (e.g., ps_6b5b7d8737c0e0ec0a04a29a045d2d5d). |
No output schema declared.
No examples provided.
xpayr_get_supported_networks ~56
List all active EVM, TRON, Solana, and Arc Mainnet/Testnet blockchain networks, chain IDs, RPC endpoints, smart-contract splitters, and supported tokens enabled for the current API key mode.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
xpayr_get_webhook_config ~48
Inspect the merchant webhook callback URL, masked HMAC-SHA256 signing secret, and subscribed payment lifecycle events (payment.pending, payment.completed, payment.failed, payment.expired).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
xpayr_health_check ~36
Check XPayr Gateway API v1 operational health, version, and server timestamp (public endpoint, no API key required).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
xpayr_list_agent_payment_intents ~65
List AI agent payment intents, policy evaluation decisions, and audit trail records for the merchant.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum records to return. |
| status | string | – | Filter by decision status (approved, pending_approval, rejected, bridged). |
No output schema declared.
No examples provided.
xpayr_list_ai_agents ~33
List all AI commerce agents managed by the merchant along with their status, assigned wallets, and spending policies.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
xpayr_list_payment_sessions ~121
List merchant crypto payment sessions with optional filtering by status (pending, completed, expired, failed), currency, network, and pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Filter by token symbol (e.g., USDT, USDC). |
| limit | integer | – | Number of sessions to return per page (1-100). |
| network | string | – | Filter by blockchain network key (e.g., tron-mainnet, solana-mainnet). |
| status | string | – | Filter by session status (pending, processing, completed, expired, failed). |
No output schema declared.
No examples provided.
xpayr_reject_agent_intent ~55
Reject a pending AI agent payment intent in the merchant approval queue with an audit reason.
| Name | Type | Req | Description |
|---|---|---|---|
| intent_id | string | yes | Pending agent intent ID to reject. |
| reason | string | – | Reviewer rejection reason. |
No output schema declared.
No examples provided.
xpayr_send_test_webhook ~40
Dispatch a signed test.webhook event with HMAC-SHA256 headers to the configured merchant webhook URL to verify signature validation and delivery.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
xpayr_set_webhook_endpoint ~62
Configure or update the merchant HTTPS webhook receiver URL and generate a fresh 32-byte HMAC-SHA256 signing secret.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | HTTPS webhook endpoint URL (e.g., https://mystore.com/webhooks/xpayr). |
No output schema declared.
No examples provided.
xpayr_submit_agent_payment_intent ~153
Submit an autonomous AI agent payment intent evaluated in real time against merchant spending policy guardrails (returns approved, pending_approval, or rejected).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Requested payment amount (e.g., 25.00). |
| currency | string | yes | Requested token symbol (e.g., USDC, USDT). |
| external_reference | string | – | External task, tool, or invoice correlation ID. |
| network | string | – | Target network key (e.g., arc-testnet, base-mainnet, solana-mainnet). |
| reason | string | – | Justification or invoice memo for the AI agent payment. |
| recipient_address | string | – | Destination wallet or merchant settlement address. |
No output schema declared.
No examples provided.
xpayr_update_ai_agent_policy ~161
Upsert spending policy rules for an AI commerce agent, including maximum per-transaction USD amount, daily budget cap, auto-approve threshold, and allowed blockchain networks/tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Public ID of the target AI agent. |
| allowed_currencies | array | – | List of permitted token symbols (e.g., ["USDC", "USDT"]). |
| allowed_networks | array | – | List of permitted blockchain network keys. |
| auto_approve_under | number | – | Transactions below this USD amount are auto-approved; higher amounts enter the human approval queue. |
| daily_limit_amount | number | – | Maximum daily cumulative spend in USD. |
| max_tx_amount | number | – | Maximum allowed single transaction amount in USD. |
No output schema declared.
No examples provided.
How do I install the XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP server?
XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP runs locally as an npm package, launched with npx -y xpayr-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 · xpayr-mcp
claude mcp add xpayrcom-xpayr-mcp-server -- npx -y xpayr-mcp
What is the XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP server?
XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP is listed in the public MCP registry as io.github.xpayrcom/xpayr-mcp-server. 21 MCP tools for non-custodial crypto checkout, USDT/USDC links, webhooks, and AI agents. This page covers its npm package (xpayr-mcp).
Is the XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP server safe to use?
XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP server expose?
XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP exposes 21 tools: xpayr_health_check, xpayr_create_payment_session, xpayr_get_payment_session, xpayr_list_payment_sessions, xpayr_get_public_payment_status, and 16 more. Their descriptions and schemas cost roughly 1,912 tokens of context every time the server is loaded.
Is the XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP server still maintained?
XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 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 XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP server under?
XPayr Non-Custodial Crypto Gateway & AI Agent Commerce 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.
What did VerifyMCP test on the XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP server?
VerifyMCP ran 16 checks on XPayr Non-Custodial Crypto Gateway & AI Agent Commerce MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.