io.github.h1-hunt/mintclub
NPM · MINTCLUB-MCP · SCANNED SEP 20
Trade bonding curve tokens on Base via Mint Club V2 — buy, sell, swap, create
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 110 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 127 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 527 tokens (~52/item across 10 items; 10 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; "send_token" 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 10 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.h1-hunt/mintclub MCP server?
io.github.h1-hunt/mintclub runs locally as an npm package, launched with npx -y mintclub-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 · mintclub-mcp
claude mcp add h1-hunt-mintclub -- npx -y mintclub-mcp
{
"mcpServers": {
"h1-hunt-mintclub": {
"command": "npx",
"args": [
"-y",
"mintclub-mcp"
]
}
}
} {
"servers": {
"h1-hunt-mintclub": {
"command": "npx",
"args": [
"-y",
"mintclub-mcp"
]
}
}
} codex mcp add h1-hunt-mintclub -- npx -y mintclub-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"h1-hunt-mintclub": {
"type": "local",
"command": [
"npx",
"-y",
"mintclub-mcp"
],
"enabled": true
}
}
} openclaw mcp add h1-hunt-mintclub --command npx --arg -y --arg mintclub-mcp
mcp_servers:
h1-hunt-mintclub:
command: "npx"
args: ["-y", "mintclub-mcp"] {
"McpServers": {
"h1-hunt-mintclub": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mintclub-mcp"
]
}
}
} assistant mcp add h1-hunt-mintclub -t stdio -c npx -a -y mintclub-mcp
{
"mcpServers": {
"h1-hunt-mintclub": {
"command": "npx",
"args": [
"-y",
"mintclub-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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Security disclosure: unverified → pass ▲ functional
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: pass → unverified ▼ functional
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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/mintclub-mcp@0.1.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 110 packages
| Packages resolved | 110 |
|---|---|
| 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 →
buy_token ~42
Buy (mint) bonding curve tokens with reserve token
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount of tokens to buy |
| token | string | yes | Token address or symbol |
No output schema declared.
No examples provided.
create_token ~93
Create a new bonding curve token
| Name | Type | Req | Description |
|---|---|---|---|
| curve | string | – | Curve preset: linear, exponential, logarithmic, flat |
| finalPrice | string | – | Final price |
| initialPrice | string | – | Starting price |
| maxSupply | string | yes | Maximum supply |
| name | string | yes | Token name |
| reserve | string | yes | Reserve token address or symbol |
| symbol | string | yes | Token symbol |
No output schema declared.
No examples provided.
sell_token ~42
Sell (burn) bonding curve tokens for reserve token
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount of tokens to sell |
| token | string | yes | Token address or symbol |
No output schema declared.
No examples provided.
send_token ~53
Send ETH or ERC-20 tokens to an address
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to send |
| to | string | yes | Recipient address |
| token | string | – | Token symbol or address (omit for ETH) |
No output schema declared.
No examples provided.
swap ~83
Swap tokens via Uniswap V3/V4 (any pair, auto-routes)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount of input token |
| inputToken | string | yes | Input token (ETH, HUNT, USDC, or address) |
| outputToken | string | yes | Output token |
| slippage | string | – | Slippage tolerance % (default: 1) |
No output schema declared.
No examples provided.
token_info ~39
Get Mint Club V2 token info: price, supply, reserve, bonding curve, USD values
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Token address or symbol |
No output schema declared.
No examples provided.
token_price ~28
Get token price in reserve token and USD
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Token address or symbol |
No output schema declared.
No examples provided.
wallet_balance ~19
Get wallet address and balances (ETH + known tokens)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zap_buy ~65
Buy bonding curve tokens with any token (auto-swaps via Uniswap)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount of input token to spend |
| inputToken | string | yes | Token to pay with (ETH, USDC, etc.) |
| token | string | yes | Token to buy |
No output schema declared.
No examples provided.
zap_sell ~63
Sell bonding curve tokens for any token (auto-swaps via Uniswap)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount of tokens to sell |
| outputToken | string | yes | Token to receive (ETH, USDC, etc.) |
| token | string | yes | Token to sell |
No output schema declared.
No examples provided.
What is the io.github.h1-hunt/mintclub MCP server?
io.github.h1-hunt/mintclub is an MCP server listed in the public MCP registry as io.github.h1-hunt/mintclub. Trade bonding curve tokens on Base via Mint Club V2, buy, sell, swap, create. This page covers its npm package (mintclub-mcp).
Is the io.github.h1-hunt/mintclub MCP server safe to use?
io.github.h1-hunt/mintclub 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.h1-hunt/mintclub MCP server expose?
io.github.h1-hunt/mintclub exposes 10 tools: token_info, token_price, wallet_balance, buy_token, sell_token, and 5 more. Their descriptions and schemas cost roughly 527 tokens of context every time the server is loaded.
Is the io.github.h1-hunt/mintclub MCP server still maintained?
io.github.h1-hunt/mintclub 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.h1-hunt/mintclub MCP server under?
io.github.h1-hunt/mintclub declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.