io.github.MintwareDevelopers/mcp-server
NPM · @MINTWAREHQ/MCP-SERVER · SCANNED SEP 20
Look up on-chain Attribution reputation scores for wallets and AI agents on Base.
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
- 32 of 111 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 24 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
- Context-footprint check failed: tool/resource definitions use about 1221 tokens (~111/item across 11 items; 11 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 Management83
- Stability observed for 25 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; "mintware_x402_pay" implies "pay" 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 11 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.MintwareDevelopers/mcp-server server?
io.github.MintwareDevelopers/mcp-server runs locally as an npm package, launched with npx -y @mintwarehq/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mintwarehq/mcp-server
claude mcp add mintwaredevelopers-mcp-server -- npx -y @mintwarehq/mcp-server
{
"mcpServers": {
"mintwaredevelopers-mcp-server": {
"command": "npx",
"args": [
"-y",
"@mintwarehq/mcp-server"
]
}
}
} {
"servers": {
"mintwaredevelopers-mcp-server": {
"command": "npx",
"args": [
"-y",
"@mintwarehq/mcp-server"
]
}
}
} codex mcp add mintwaredevelopers-mcp-server -- npx -y @mintwarehq/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mintwaredevelopers-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@mintwarehq/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add mintwaredevelopers-mcp-server --command npx --arg -y --arg @mintwarehq/mcp-server
mcp_servers:
mintwaredevelopers-mcp-server:
command: "npx"
args: ["-y", "@mintwarehq/mcp-server"] {
"McpServers": {
"mintwaredevelopers-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mintwarehq/mcp-server"
]
}
}
} assistant mcp add mintwaredevelopers-mcp-server -t stdio -c npx -a -y @mintwarehq/mcp-server
{
"mcpServers": {
"mintwaredevelopers-mcp-server": {
"command": "npx",
"args": [
"-y",
"@mintwarehq/mcp-server"
]
}
}
} 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 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 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.
- 4 Sept 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.
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/@mintwarehq/mcp-server@0.1.3
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 111 packages
| Packages resolved | 111 |
|---|---|
| Stale | 31 |
| No linked repository | 1 |
| 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 →
mintware_claim_pending ~130
Fetch pending oracle-signed action attestations from the Mintware API and submit them to the AIAttribution contract on Base mainnet. This updates the agent's on-chain score. The agent wallet pays gas for each submitted attestation. Run this periodically to keep the Attribution score current. Requires the wallet address and private key.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum wallet address of the agent (0x-prefixed, 42 characters) |
| privateKey | string | yes | Private key of the agent wallet (0x-prefixed hex, 66 characters). Signs the claim transactions on Base mainnet. |
No output schema declared.
No examples provided.
mintware_get_score ~127
Fetch the Mintware AI Attribution score for an agent wallet address on Base mainnet. Returns the total score, rank, and breakdown across four dimensions: behavior (how well the agent follows instructions and avoids harmful outputs), contribution (value created for users and the ecosystem), interpretability (transparency via Model Workspace Protocol hash submissions), and risk (penalty for unsafe or manipulative actions). Also returns PnL data if available and whether the agent is a Transparent Agent.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum wallet address of the AI agent (0x-prefixed, 42 characters) |
No output schema declared.
No examples provided.
mintware_leaderboard ~84
Fetch the top AI agents on the Mintware Attribution leaderboard on Base mainnet. Returns agents ranked by total Attribution score, with address, score, and transparent status. Use this to discover high-performing agents, compare scores, or find the current rank leaders.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of agents to return (default: 10, max: 50) |
No output schema declared.
No examples provided.
mintware_parking_account ~105
Show an agent's Mintware capital-parking account: how much USDC is parked (and earning yield) and how much is spendable in place right now. Mintware lets an agent park idle USDC in a yield vault where it earns, and spend it per call over x402 without ever un-parking — parking never locks. Read-only, no key required.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Agent wallet address (0x-prefixed, 42 chars). |
No output schema declared.
No examples provided.
mintware_pools ~47
Mintware's liquidity manifest for solver/aggregator networks (UniswapX, CoW, 1inch). Machine-readable pool discovery for routers — not a user-facing pool list.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mintware_register ~125
Register an AI agent wallet with the Mintware AI Attribution contract on Base mainnet. This is a one-time on-chain transaction — the wallet pays a small amount of ETH gas. After registration, the oracle watcher begins tracking the agent's on-chain activity automatically. Requires the wallet's private key. IMPORTANT: only pass a private key for wallets you control and only in a trusted, secure environment.
| Name | Type | Req | Description |
|---|---|---|---|
| privateKey | string | yes | Private key of the agent wallet to register (0x-prefixed hex, 66 characters). This key signs the registration transaction on Base mainnet. |
No output schema declared.
No examples provided.
mintware_swap_quote ~195
Get an executable swap quote via Mintware's LI.FI proxy. Returns LI.FI's raw quote INCLUDING the `transactionRequest` (to, data, value) — so the AGENT signs and broadcasts it with its own wallet key. This tool does NOT move funds or sign anything; it only returns the quote for the agent to execute. Amounts are raw token units (wei/atomic). `taker` is the agent's own address.
| Name | Type | Req | Description |
|---|---|---|---|
| buyToken | string | yes | Token address being bought (0x…). |
| chainId | number | yes | EVM chain id (e.g. 8453 for Base). |
| sellAmount | string | yes | Amount to sell, in raw token units (atomic/wei). |
| sellToken | string | yes | Token address being sold (0x…). |
| taker | string | yes | The agent's own wallet address (receives the bought token). |
No output schema declared.
No examples provided.
mintware_vault_list ~92
List Mintware liquidity vaults (dual-sided, reputation-adjacent DeFi on Uniswap V4). Returns each vault with its current epoch (pool, bonus pool, status, deadline). Optional status filter. NOTE: vaults are currently in testing on Base Sepolia — read-only discovery, not for real deposits yet.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Optional filter, e.g. 'active'. |
No output schema declared.
No examples provided.
mintware_x402_pay ~177
Pay for an x402-gated compute/API call in USDC and return the resource. Reads the 402 challenge, enforces the optional maxAmountUsd cap, signs an EIP-3009 USDC authorization with the provided key, retries with the payment, and returns the resource body. IMPORTANT: only pass a private key for a wallet you control, in a trusted environment. Use mintware_x402_quote first to preview cost.
| Name | Type | Req | Description |
|---|---|---|---|
| maxAmountUsd | number | – | Hard cap on what to pay, in USD. Aborts if the price exceeds it. |
| privateKey | string | yes | Private key of the paying wallet (0x-prefixed hex, 66 chars). Signs the EIP-3009 authorization. |
| url | string | yes | The x402-protected resource URL to pay for and fetch. |
No output schema declared.
No examples provided.
mintware_x402_quote ~76
Preflight an x402-gated compute/API URL WITHOUT paying. Returns the price (USDC), network, recipient, and description advertised in the HTTP 402 challenge, so you can decide whether to pay. Read-only, no key required.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The x402-protected resource URL to quote. |
No output schema declared.
No examples provided.
mintware_yields ~63
Live yield benchmarks — a curated set of real DeFi pools (base APY, from DefiLlama) that Mintware references. Use this when an agent is comparing where idle capital could earn. Returns { ok, source, asOf, rows }.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.MintwareDevelopers/mcp-server server?
io.github.MintwareDevelopers/mcp-server is listed in the public MCP registry as io.github.MintwareDevelopers/mcp-server. Look up on-chain Attribution reputation scores for wallets and AI agents on Base. This page covers its npm package (@mintwarehq/mcp-server).
Is the io.github.MintwareDevelopers/mcp-server server safe to use?
io.github.MintwareDevelopers/mcp-server 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.MintwareDevelopers/mcp-server server expose?
io.github.MintwareDevelopers/mcp-server exposes 11 tools: mintware_get_score, mintware_leaderboard, mintware_register, mintware_claim_pending, mintware_parking_account, and 6 more. Their descriptions and schemas cost roughly 1,221 tokens of context every time the server is loaded.
Is the io.github.MintwareDevelopers/mcp-server server still maintained?
io.github.MintwareDevelopers/mcp-server 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.MintwareDevelopers/mcp-server server under?
io.github.MintwareDevelopers/mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.