io.github.vdappdev2/marketplace
NPM · @VERUSIDX/MARKETPLACE-MCP · SCANNED SEP 20
MCP server for Verus on-chain marketplace — create, browse, accept, and close offers
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 97 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 132 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1278 tokens (~255/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.vdappdev2/marketplace MCP server?
io.github.vdappdev2/marketplace runs locally as an npm package, launched with npx -y @verusidx/marketplace-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 · @verusidx/marketplace-mcp
claude mcp add vdappdev2-marketplace -- npx -y @verusidx/marketplace-mcp
{
"mcpServers": {
"vdappdev2-marketplace": {
"command": "npx",
"args": [
"-y",
"@verusidx/marketplace-mcp"
]
}
}
} {
"servers": {
"vdappdev2-marketplace": {
"command": "npx",
"args": [
"-y",
"@verusidx/marketplace-mcp"
]
}
}
} codex mcp add vdappdev2-marketplace -- npx -y @verusidx/marketplace-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vdappdev2-marketplace": {
"type": "local",
"command": [
"npx",
"-y",
"@verusidx/marketplace-mcp"
],
"enabled": true
}
}
} openclaw mcp add vdappdev2-marketplace --command npx --arg -y --arg @verusidx/marketplace-mcp
mcp_servers:
vdappdev2-marketplace:
command: "npx"
args: ["-y", "@verusidx/marketplace-mcp"] {
"McpServers": {
"vdappdev2-marketplace": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@verusidx/marketplace-mcp"
]
}
}
} assistant mcp add vdappdev2-marketplace -t stdio -c npx -a -y @verusidx/marketplace-mcp
{
"mcpServers": {
"vdappdev2-marketplace": {
"command": "npx",
"args": [
"-y",
"@verusidx/marketplace-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/@verusidx/marketplace-mcp@0.1.7
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 97 packages
| Packages resolved | 97 |
|---|---|
| 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 →
closeoffers ~156
Close (cancel) open offers and reclaim the locked funds. Returns null on success. Always closes expired offers automatically, even if no parameters are given. When specific offer txids are provided, closes only those offers. Use this to cancel offers that are no longer wanted, or as periodic cleanup to reclaim funds from expired offers.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain to transact on (e.g., "VRSC", "vrsctest") |
| destination | string | – | Transparent or private address to send reclaimed funds to. |
| privatefundsdestination | string | – | Private (Sapling) address for native funds only. |
| txids | array | – | Array of offer transaction IDs to close. If omitted, closes all expired offers. |
No output schema declared.
No examples provided.
getoffers ~176
Get all open offers for a specific currency or identity. Returns both buy and sell offers — offers of the asset and offers for the asset. Use iscurrency to switch between currency offers and identity offers. Response keys are dynamic and generated by the daemon based on the queried asset — parse them dynamically. Use this to discover what's available on the market before making or taking offers.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain to query (e.g., "VRSC", "vrsctest") |
| currencyorid | string | yes | Currency name/i-address or identity name/i-address to check for offers |
| iscurrency | boolean | – | If true, look for currency offers. If false (default), look for identity offers. |
| withtx | boolean | – | If true, include serialized hex of the exchange transaction for signing. Default: false. |
No output schema declared.
No examples provided.
listopenoffers ~113
List open offers from the current wallet. Shows what this wallet has offered on-chain. Can filter by expired/unexpired status. Use this to check the status of offers the agent has created, or to find offers that need to be closed.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain to query (e.g., "VRSC", "vrsctest") |
| expired | boolean | – | Include expired offers. Default: true. |
| unexpired | boolean | – | Include unexpired (active) offers. Default: true. |
No output schema declared.
No examples provided.
makeoffer ~426
Create a new on-chain atomic swap offer. Offers are fully decentralized — no intermediary, no escrow. The offer transaction locks the offered asset on-chain until the offer is taken, expires, or is closed. Supports currency-for-currency, currency-for-identity, identity-for-currency, and identity-for-identity swaps. For currency offers, use {"currency": "name", "amount": n}. For identity offers (without control tokens), use {"identity": "name@"} or a full identity definition. If an identity has a control token (flags: 5), offer/request the control token as a currency instead: {"currency": "idname.parent", "amount": 0.00000001}. Always include parent in identity definitions.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain to transact on (e.g., "VRSC", "vrsctest") |
| changeaddress | string | yes | Transparent address or VerusID ("ID@") for change. |
| expiryheight | number | – | Block height at which this offer expires. Default: current height + 20 (~20 minutes). Set higher for marketplace listings. |
| feeamount | number | – | Custom fee amount. Default: 0.0001. |
| for | object | yes | What to accept in return — {"currency": "name", "amount": n, "address": "dest"} for currency (address is REQUIRED — can be R-address, VerusID name@, or i-address), or full identity definition (with p… |
| fromaddress | string | yes | Source address for funds. If the user has not specified a preferred address, ask which address to use or if they prefer a wildcard ("*", "R*", "i*", or "z*" for private txs). |
| offer | object | yes | What to offer — {"currency": "name", "amount": n} for currency, or {"identity": "name@"} / full identity definition for identity. |
| returntx | boolean | – | If true, return signed transaction hex instead of broadcasting. Default: false. |
No output schema declared.
No examples provided.
takeoffer ~407
Accept an existing on-chain offer. Creates and posts a transaction that atomically executes the exchange — both sides swap in a single transaction, or neither does. The offer transaction must have at least 1 confirmation before it can be taken. Before taking, verify the offer hasn't expired by checking blockexpiry against current block height. deliver is what you give, accept is what you get. For currency: deliver {"currency": "name", "amount": n}, accept {"address": "addr", "currency": "name", "amount": n}. For identity: deliver "name@" (string), accept is full identity definition with parent. If the identity has a control token, use control token currency instead.
| Name | Type | Req | Description |
|---|---|---|---|
| accept | object | yes | What the taker receives — {"address": "addr", "currency": "name", "amount": n} (currency) or full identity definition (identity). |
| chain | string | yes | Chain to transact on (e.g., "VRSC", "vrsctest") |
| changeaddress | string | yes | Transparent address or VerusID for change. |
| deliver | – | yes | What the taker delivers — "name@" (identity) or {"currency": "name", "amount": n} (currency). |
| feeamount | number | – | Custom fee amount. Default: 0.0001. |
| fromaddress | string | yes | Source address for funds. If the user has not specified a preferred address, ask which address to use or if they prefer a wildcard ("*", "R*", "i*", or "z*" for private txs). |
| returntx | boolean | – | If true, return signed transaction hex instead of broadcasting. Default: false. |
| tx | string | – | Hex transaction to complete (from makeoffer with returntx=true). Either txid or tx is required. |
| txid | string | – | Transaction ID of the offer to accept (from getoffers or makeoffer). Either txid or tx is required. |
No output schema declared.
No examples provided.
What is the io.github.vdappdev2/marketplace MCP server?
io.github.vdappdev2/marketplace is an MCP server listed in the public MCP registry as io.github.vdappdev2/marketplace. MCP server for Verus on-chain marketplace, create, browse, accept, and close offers. This page covers its npm package (@verusidx/marketplace-mcp).
Is the io.github.vdappdev2/marketplace MCP server safe to use?
io.github.vdappdev2/marketplace scores 81 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.vdappdev2/marketplace MCP server expose?
io.github.vdappdev2/marketplace exposes 5 tools: getoffers, listopenoffers, makeoffer, takeoffer, closeoffers. Their descriptions and schemas cost roughly 1,278 tokens of context every time the server is loaded.
Is the io.github.vdappdev2/marketplace MCP server still maintained?
io.github.vdappdev2/marketplace 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.vdappdev2/marketplace MCP server under?
io.github.vdappdev2/marketplace declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.