io.github.jams24/inventpay-mcp
NPM · INVENTPAY-MCP · SCANNED SEP 20
Manage crypto payments, stores, digital products, and orders via InventPay
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 Security98
- 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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 23 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1343 tokens (~79/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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; "delete_product" implies "delete" 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 17 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.jams24/inventpay-mcp server?
io.github.jams24/inventpay-mcp runs locally as an npm package, launched with npx -y inventpay-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 · inventpay-mcp
claude mcp add jams24-inventpay-mcp -- npx -y inventpay-mcp
{
"mcpServers": {
"jams24-inventpay-mcp": {
"command": "npx",
"args": [
"-y",
"inventpay-mcp"
]
}
}
} {
"servers": {
"jams24-inventpay-mcp": {
"command": "npx",
"args": [
"-y",
"inventpay-mcp"
]
}
}
} codex mcp add jams24-inventpay-mcp -- npx -y inventpay-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jams24-inventpay-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"inventpay-mcp"
],
"enabled": true
}
}
} openclaw mcp add jams24-inventpay-mcp --command npx --arg -y --arg inventpay-mcp
mcp_servers:
jams24-inventpay-mcp:
command: "npx"
args: ["-y", "inventpay-mcp"] {
"McpServers": {
"jams24-inventpay-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"inventpay-mcp"
]
}
}
} assistant mcp add jams24-inventpay-mcp -t stdio -c npx -a -y inventpay-mcp
{
"mcpServers": {
"jams24-inventpay-mcp": {
"command": "npx",
"args": [
"-y",
"inventpay-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 +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.
- 18 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 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.
- 13 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.
- 11 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.
- 10 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/inventpay-mcp@1.0.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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
create_invoice ~112
Create a multi-currency invoice. The customer can choose which cryptocurrency to pay with. Returns an invoice URL.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Invoice amount |
| amountCurrency | string | – | Currency the amount is denominated in |
| callbackUrl | string | – | Webhook URL for payment status notifications |
| description | string | – | Invoice description |
| expirationMinutes | number | – | Invoice expiration in minutes (5-1440, default 60) |
| orderId | string | – | Your internal order/reference ID |
No output schema declared.
No examples provided.
create_payment ~130
Create a crypto payment. Returns a unique wallet address, QR code, and invoice URL for the customer to pay.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Payment amount |
| amountCurrency | string | – | Currency the amount is denominated in |
| callbackUrl | string | – | Webhook URL for payment status notifications |
| currency | string | yes | Cryptocurrency the customer will pay with |
| description | string | – | Payment description shown to the customer |
| expirationMinutes | number | – | Payment expiration in minutes (5-1440, default 30) |
| orderId | string | – | Your internal order/reference ID |
No output schema declared.
No examples provided.
create_product ~166
Add a digital product to your store. Products are priced in USDT and auto-converted to crypto at checkout. Attach digitalContent for automatic delivery after payment.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Product description (max 5000 characters) |
| digitalContent | object | – | Digital delivery content — auto-delivered after payment |
| images | array | – | Array of HTTPS image URLs (max 10) |
| metadata | object | – | Custom key-value metadata |
| name | string | yes | Product name (1-200 characters) |
| price | number | yes | Price in USDT (0.01 - 1,000,000) |
| stock | number | – | Available quantity. Omit for unlimited stock. |
| variants | array | – | Variant options (e.g., size, tier) |
No output schema declared.
No examples provided.
create_store ~109
Create a new merchant storefront. Each merchant gets one store with a unique URL slug. Customers can browse and purchase digital products with crypto.
| Name | Type | Req | Description |
|---|---|---|---|
| banner | string | – | HTTPS URL for the store banner image |
| description | string | – | Store description (max 1000 characters) |
| logo | string | – | HTTPS URL for the store logo |
| name | string | yes | Store name (2-100 characters). A URL slug will be auto-generated. |
| settings | object | – | Custom store settings |
No output schema declared.
No examples provided.
create_withdrawal ~79
Create a withdrawal request to send funds to an external wallet address. Requires 2FA if enabled on the account.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to withdraw |
| currency | string | yes | Cryptocurrency to withdraw |
| description | string | – | Withdrawal description/memo |
| destinationAddress | string | yes | External wallet address to send funds to |
No output schema declared.
No examples provided.
delete_product ~41
Deactivate a product from your store. Products with existing orders are soft-deleted (hidden, not removed).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Product ID to deactivate |
No output schema declared.
No examples provided.
get_balances ~33
Get all cryptocurrency balances for your merchant account. Shows available, pending, total earned, and total withdrawn for each currency.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_order ~36
Get full details of a specific order including items, payment status, customer info, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Order ID |
No output schema declared.
No examples provided.
get_payment_status ~43
Check the current status of a payment or invoice. Returns status, amount, confirmations, and transaction details.
| Name | Type | Req | Description |
|---|---|---|---|
| paymentId | string | yes | The payment or invoice ID |
No output schema declared.
No examples provided.
get_store ~26
Get your store details including name, slug, URL, product count, and order count.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_store_analytics ~30
Get store analytics: total orders, revenue breakdown by status, product count, and recent order activity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_withdrawal ~41
Check the status of a withdrawal request. Returns status, amount, transaction hash, and processing details.
| Name | Type | Req | Description |
|---|---|---|---|
| withdrawalId | string | yes | The withdrawal ID |
No output schema declared.
No examples provided.
list_orders ~64
List all orders for your store with optional status filter and pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Items per page, 1-50 (default 20) |
| page | number | – | Page number (default 1) |
| status | string | – | Filter by order status |
No output schema declared.
No examples provided.
list_products ~63
List all products in your store with optional search and pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Items per page, 1-50 (default 20) |
| page | number | – | Page number (default 1) |
| search | string | – | Search products by name |
No output schema declared.
No examples provided.
update_order_status ~92
Update the fulfillment status of an order. Valid transitions: PAID→PROCESSING, PROCESSING→SHIPPED/COMPLETED, SHIPPED→COMPLETED, COMPLETED→REFUNDED. Digital orders auto-transition to COMPLETED.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Order ID |
| notes | string | – | Optional notes about this status change |
| status | string | yes | New order status |
No output schema declared.
No examples provided.
update_product ~174
Update a product in your store. Only provided fields are changed. Updating the name regenerates the slug.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Product description (max 5000 characters) |
| digitalContent | object | – | Digital delivery content — auto-delivered after payment |
| id | string | yes | Product ID |
| images | array | – | Array of HTTPS image URLs (max 10) |
| isActive | boolean | – | Toggle product visibility |
| metadata | object | – | Custom key-value metadata |
| name | string | – | Product name (1-200 characters) |
| price | number | – | Price in USDT (0.01 - 1,000,000) |
| sortOrder | number | – | Display order (0-9999) |
| stock | number | – | Available quantity (0-999,999) |
No output schema declared.
No examples provided.
update_store ~104
Update your store details. Only provided fields are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| banner | string | – | HTTPS URL for the store banner image |
| description | string | – | Store description (max 1000 characters) |
| isActive | boolean | – | Toggle store visibility (true = live, false = hidden) |
| logo | string | – | HTTPS URL for the store logo |
| name | string | – | Store name (2-100 characters) |
| settings | object | – | Custom store settings |
No output schema declared.
No examples provided.
What is the io.github.jams24/inventpay-mcp server?
io.github.jams24/inventpay-mcp is listed in the public MCP registry as io.github.jams24/inventpay-mcp. Manage crypto payments, stores, digital products, and orders via InventPay. This page covers its npm package (inventpay-mcp).
Is the io.github.jams24/inventpay-mcp server safe to use?
io.github.jams24/inventpay-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting 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.jams24/inventpay-mcp server expose?
io.github.jams24/inventpay-mcp exposes 17 tools: create_payment, create_invoice, get_payment_status, get_balances, create_withdrawal, and 12 more. Their descriptions and schemas cost roughly 1,343 tokens of context every time the server is loaded.
Is the io.github.jams24/inventpay-mcp server still maintained?
io.github.jams24/inventpay-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.jams24/inventpay-mcp server under?
io.github.jams24/inventpay-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.