io.github.csacanam/voulti
NPM · VOULTI-MCP · SCANNED SEP 20
Accept crypto payments from AI agents: invoices + hosted checkout on 5 chains. No API key.
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 & 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 43 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 334 tokens (~111/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.csacanam/voulti MCP server?
io.github.csacanam/voulti runs locally as an npm package, launched with npx -y voulti-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 · voulti-mcp
claude mcp add csacanam-voulti -- npx -y voulti-mcp
{
"mcpServers": {
"csacanam-voulti": {
"command": "npx",
"args": [
"-y",
"voulti-mcp"
]
}
}
} {
"servers": {
"csacanam-voulti": {
"command": "npx",
"args": [
"-y",
"voulti-mcp"
]
}
}
} codex mcp add csacanam-voulti -- npx -y voulti-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"csacanam-voulti": {
"type": "local",
"command": [
"npx",
"-y",
"voulti-mcp"
],
"enabled": true
}
}
} openclaw mcp add csacanam-voulti --command npx --arg -y --arg voulti-mcp
mcp_servers:
csacanam-voulti:
command: "npx"
args: ["-y", "voulti-mcp"] {
"McpServers": {
"csacanam-voulti": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"voulti-mcp"
]
}
}
} assistant mcp add csacanam-voulti -t stdio -c npx -a -y voulti-mcp
{
"mcpServers": {
"csacanam-voulti": {
"command": "npx",
"args": [
"-y",
"voulti-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.
- 19 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.
- 17 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 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.
- 12 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.
- 10 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 9 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- 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/voulti-mcp@0.1.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 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 ~178
Create a payment invoice and get a hosted checkout link to send to the payer. amount_fiat is in the MERCHANT's base currency (USD, EUR, COP, ARS, BRL or MXN — confirm which one before charging; the response's fiat_currency tells you). Invoices expire in 1 hour by default; pass expires_at (ISO 8601) for slow payers. Use reference to tag the invoice with your own order id or client name.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_fiat | number | yes | Amount in the merchant's base currency |
| commerce_id | string | – | Merchant id (defaults to VOULTI_COMMERCE_ID env) |
| expires_at | string | – | ISO 8601 expiration (default: 1 hour from now) |
| reference | string | – | Your own memo: order id, client name… |
No output schema declared.
No examples provided.
get_invoice ~84
Check an invoice's payment status. status: Pending → Paid | Expired. On Paid it includes paid_tx_hash (on-chain proof), payment_method and paid_at. Poll every few seconds while the payer is at checkout. Verify Paid here before releasing goods — even if you also receive a webhook.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | Invoice id (data.id from create_invoice) |
No output schema declared.
No examples provided.
get_payment_link ~72
Get the merchant's PERMANENT payment page link, where the payer types the amount themselves. Never expires. Good for tips, donations or 'pay what you owe' — for fixed amounts prefer create_invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| commerce_id | string | – | Merchant id (defaults to VOULTI_COMMERCE_ID env) |
No output schema declared.
No examples provided.
What is the io.github.csacanam/voulti MCP server?
io.github.csacanam/voulti is an MCP server listed in the public MCP registry as io.github.csacanam/voulti. Accept crypto payments from AI agents: invoices + hosted checkout on 5 chains. No API key. This page covers its npm package (voulti-mcp).
Is the io.github.csacanam/voulti MCP server safe to use?
io.github.csacanam/voulti scores 84 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.csacanam/voulti MCP server expose?
io.github.csacanam/voulti exposes 3 tools: create_invoice, get_invoice, get_payment_link. Their descriptions and schemas cost roughly 334 tokens of context every time the server is loaded.
Is the io.github.csacanam/voulti MCP server still maintained?
io.github.csacanam/voulti 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.csacanam/voulti MCP server under?
io.github.csacanam/voulti declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.