io.github.Yummybait-fin/uniswap-tx-builder-mcp
NPM · @YUMMYBAIT/UNISWAP-TX-BUILDER-MCP · 2 COMPONENTS · SCANNED SEP 20
Builds and simulates unsigned Uniswap v3 liquidity-position transactions — keyless, never signs.
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 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Yummybait-fin/uniswap-tx-builder-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 53 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2057 tokens (~187/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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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.Yummybait-fin/uniswap-tx-builder-mcp server?
io.github.Yummybait-fin/uniswap-tx-builder-mcp runs locally as an npm package, launched with npx -y @yummybait/uniswap-tx-builder-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 · @yummybait/uniswap-tx-builder-mcp
claude mcp add yummybait-fin-uniswap-tx-builder-mcp -- npx -y @yummybait/uniswap-tx-builder-mcp
{
"mcpServers": {
"yummybait-fin-uniswap-tx-builder-mcp": {
"command": "npx",
"args": [
"-y",
"@yummybait/uniswap-tx-builder-mcp"
]
}
}
} {
"servers": {
"yummybait-fin-uniswap-tx-builder-mcp": {
"command": "npx",
"args": [
"-y",
"@yummybait/uniswap-tx-builder-mcp"
]
}
}
} codex mcp add yummybait-fin-uniswap-tx-builder-mcp -- npx -y @yummybait/uniswap-tx-builder-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yummybait-fin-uniswap-tx-builder-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@yummybait/uniswap-tx-builder-mcp"
],
"enabled": true
}
}
} openclaw mcp add yummybait-fin-uniswap-tx-builder-mcp --command npx --arg -y --arg @yummybait/uniswap-tx-builder-mcp
mcp_servers:
yummybait-fin-uniswap-tx-builder-mcp:
command: "npx"
args: ["-y", "@yummybait/uniswap-tx-builder-mcp"] {
"McpServers": {
"yummybait-fin-uniswap-tx-builder-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@yummybait/uniswap-tx-builder-mcp"
]
}
}
} assistant mcp add yummybait-fin-uniswap-tx-builder-mcp -t stdio -c npx -a -y @yummybait/uniswap-tx-builder-mcp
{
"mcpServers": {
"yummybait-fin-uniswap-tx-builder-mcp": {
"command": "npx",
"args": [
"-y",
"@yummybait/uniswap-tx-builder-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 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.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 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.
- 14 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.
- 12 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.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
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/@yummybait/uniswap-tx-builder-mcp@0.4.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Yummybait-fin/uniswap-tx-builder-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Yummybait-fin/uniswap-tx-builder-mcp/.github/workflows/release.yml@refs/tags/v0.4.3 |
| Rekor log index | 2268677496 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9cf0d942e7bcc742101ecf4d164ebfa4f5297bfe23c8328da066a67d595d874da2ed21ad4e9f29cd9184958f0054812d0c66058d66e14e684b1263cf0 |
Background: How many MCP packages publish verified provenance →
Dependencies 111 packages
| Packages resolved | 111 |
|---|---|
| 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 →
build_approve Build an ERC-20 approve transaction ~165
Build an UNSIGNED tx that approves `spender` to move up to `amount` of `token` on behalf of the wallet that signs it — e.g. the NonfungiblePositionManager before build_mint/build_increase, or Permit2 before a Permit2-paid build_swap. Pass amount="max" for an unlimited (uint256 max) allowance. Returns the tx plus unsigned rlp; when simulated, simulationResult={approved} decoded from the eth_call return data. Pass `sender` (the signing wallet) to eth_call-simulate before signing.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | – | yes | – |
| chainId | integer | yes | – |
| sender | string | – | – |
| simulate | boolean | – | – |
| spender | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
build_close Build a close-position transaction ~149
Build an UNSIGNED tx that removes all liquidity and collects everything from a Uniswap v3 position (multicalls when needed). Returns the tx (+ unsigned rlp) plus the read position. When simulated, simulationResult={decreaseLiquidity?: {amount0,amount1}, collect: {amount0,amount1}} decoded from the eth_call return data. Set burn=true to also burn the now-empty NFT in the same multicall. Set simulate=false to skip the eth_call dry-run (on by default).
| Name | Type | Req | Description |
|---|---|---|---|
| burn | boolean | – | – |
| chainId | integer | yes | – |
| positionId | string | yes | – |
| recipient | string | yes | – |
| simulate | boolean | – | – |
No output schema declared.
No examples provided.
build_collect Build a collect-fees transaction ~125
Build an UNSIGNED tx that collects all uncollected fees from a Uniswap v3 position to `recipient`. Returns tx={to,data,value,chainId} plus rlp (the unsigned EIP-1559 serialization for signing services). When simulated, simulationResult={amount0,amount1} — the actual amounts eth_call reports would be collected. Set simulate=false to skip the eth_call dry-run (on by default).
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | yes | – |
| positionId | string | yes | – |
| recipient | string | yes | – |
| simulate | boolean | – | – |
No output schema declared.
No examples provided.
build_increase Build an increase-liquidity transaction ~159
Build an UNSIGNED tx that adds liquidity to an EXISTING Uniswap v3 position. Amounts are decimal strings (wei); mins are derived from slippageBps (default 0.5%). Returns the tx plus unsigned rlp. When simulated, simulationResult={liquidity,amount0,amount1} decoded from the eth_call return data. Simulation is OFF by default (needs token approvals + balances); pass simulate=true to attempt it.
| Name | Type | Req | Description |
|---|---|---|---|
| amount0Desired | string | yes | – |
| amount1Desired | string | yes | – |
| chainId | integer | yes | – |
| positionId | string | yes | – |
| recipient | string | yes | – |
| simulate | boolean | – | – |
| slippageBps | integer | – | – |
No output schema declared.
No examples provided.
build_mint Build a mint-position transaction ~209
Build an UNSIGNED tx that mints a new Uniswap v3 position. Amounts are decimal strings (wei) — compute them with get_pool_state (live ratio) right before minting, or stale prices revert the mint. Returns the tx plus unsigned rlp. When simulated, simulationResult={tokenId,liquidity,amount0,amount1} decoded from the eth_call return data. Simulation is OFF by default here (minting needs token approvals and balances, so eth_call usually reverts); pass simulate=true to attempt it.
| Name | Type | Req | Description |
|---|---|---|---|
| amount0Desired | string | yes | – |
| amount1Desired | string | yes | – |
| chainId | integer | yes | – |
| fee | integer | yes | – |
| recipient | string | yes | – |
| simulate | boolean | – | – |
| slippageBps | integer | – | – |
| tickLower | integer | yes | – |
| tickUpper | integer | yes | – |
| token0 | string | yes | – |
| token1 | string | yes | – |
No output schema declared.
No examples provided.
build_swap Build a token→token swap transaction (Universal Router) ~436
Build an UNSIGNED tx that swaps `amountInWei` of `tokenIn` for `tokenOut` (exact-in, single hop through the `fee` pool) via the Universal Router. By default `tokenIn` pays via Permit2. When `sender` is given and Permit2 has no sufficient standing allowance for the Universal Router, this returns {permit2Required: true, typedData, permit} instead of a tx — sign `typedData` with `sender`'s wallet (e.g. sign_typed_data), then call build_swap again with the same args plus permit2=<the returned "permit"> and permit2Signature=<the signature> to get the tx, with a PERMIT2_PERMIT command embedded ahead of the swap — no separate on-chain Permit2 approval tx ever needed. With `wrapWei` (≥ amountInWei, requires tokenIn = WETH9) the tx is payable and wraps that much native ETH first, swaps amountInWei of it, and sweeps the WETH remainder — use this when the wallet holds native ETH instead of WETH (mutually exclusive with Permit2 payment/`permit2`). With `unwrapOut` (requires tokenOut = WETH9) the swap output is unwrapped to native ETH before reaching `recipient` — use this to sell a token for ETH. `wrapWei` and `unwrapOut` are mutually exclusive. `recipient` defaults to the tx sender. Returns the tx plus unsigned rlp. Pass `sender` to eth_call-simulate before signing.
| Name | Type | Req | Description |
|---|---|---|---|
| amountInWei | string | yes | – |
| amountOutMin | string | yes | – |
| chainId | integer | yes | – |
| deadline | integer | – | – |
| fee | integer | yes | – |
| permit2 | object | – | – |
| permit2Signature | string | – | – |
| recipient | string | – | – |
| sender | string | – | – |
| simulate | boolean | – | – |
| tokenIn | string | yes | – |
| tokenOut | string | yes | – |
| unwrapOut | boolean | – | – |
| wrapWei | string | – | – |
No output schema declared.
No examples provided.
build_wrap Build a wrap-native-ETH transaction (Universal Router) ~140
Build an UNSIGNED payable tx that wraps `amountWei` native ETH into WETH via the Universal Router WRAP_ETH command (works under UR-allowlisting wallet policies where a direct WETH.deposit() doesn't). `recipient` defaults to the tx sender — omit it unless the WETH should go elsewhere. Returns the tx plus unsigned rlp. Pass `sender` (the signing wallet) to eth_call-simulate before signing.
| Name | Type | Req | Description |
|---|---|---|---|
| amountWei | string | yes | – |
| chainId | integer | yes | – |
| deadline | integer | – | – |
| recipient | string | – | – |
| sender | string | – | – |
| simulate | boolean | – | – |
No output schema declared.
No examples provided.
get_pool_state Read live pool state; plan a range and mint amounts from it ~214
READ-ONLY (builds no tx). Returns the pool's LIVE state: pool address, tick, sqrtPriceX96, price (token1 per token0, human units), tickSpacing. With rangePct: suggested tickLower/tickUpper within ±pct of spot, rounded INWARD to tick spacing. With balance0+balance1 (raw wei) + tickLower/tickUpper: amount0Desired/amount1Desired for build_mint computed from the live sqrtPrice ratio, plus which side limits. Errors if spot is outside the range. ALWAYS recompute amounts with this right before build_mint — stale ratios revert with 'Price slippage check'.
| Name | Type | Req | Description |
|---|---|---|---|
| balance0 | string | – | – |
| balance1 | string | – | – |
| chainId | integer | yes | – |
| fee | integer | yes | – |
| rangePct | number | – | – |
| tickLower | integer | – | – |
| tickUpper | integer | – | – |
| token0 | string | yes | – |
| token1 | string | yes | – |
No output schema declared.
No examples provided.
get_positions List a wallet's Uniswap v3 positions ~101
READ-ONLY (builds no tx). Lists every Uniswap v3 position NFT `owner` holds on `chainId` via the NonfungiblePositionManager, with each position's full state (token0/token1, fee, tickLower/tickUpper, liquidity, tokensOwed0/1) — feed a positionId straight into build_collect/build_close/build_increase.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | yes | – |
| owner | string | yes | – |
No output schema declared.
No examples provided.
get_swap_quote Quote a token→token swap (Uniswap v3 QuoterV2) ~197
READ-ONLY (builds no tx). Quotes an exact-in single-hop `tokenIn` → `tokenOut` swap (the same shape build_swap executes) via QuoterV2.quoteExactInputSingle — the live amountOut the pool would give at its CURRENT price, without sending a tx. Returns amountOut (wei), amountOutMin (amountOut after slippageBps, default 0.5% — feed this straight into build_swap), sqrtPriceX96After, initializedTicksCrossed, and gasEstimate. Call this immediately before build_swap: a quote read even a block earlier can go stale enough that the amountOutMin it produced reverts the swap.
| Name | Type | Req | Description |
|---|---|---|---|
| amountInWei | string | yes | – |
| chainId | integer | yes | – |
| fee | integer | yes | – |
| slippageBps | integer | – | – |
| tokenIn | string | yes | – |
| tokenOut | string | yes | – |
No output schema declared.
No examples provided.
plan_position Plan a position from a human price range ~162
READ-ONLY helper (builds no tx). Given a human price range (token1 per token0) and optional human token amounts, reads each token's decimals over RPC and returns the aligned tickLower/tickUpper (for the fee's tick spacing) plus wei amount0Desired/amount1Desired — ready to feed into build_mint. token0 must be < token1 by address. Does NOT compute the optimal amount ratio for the range.
| Name | Type | Req | Description |
|---|---|---|---|
| amount0 | string | – | – |
| amount1 | string | – | – |
| chainId | integer | yes | – |
| fee | integer | yes | – |
| priceLower | number | yes | – |
| priceUpper | number | yes | – |
| token0 | string | yes | – |
| token1 | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.Yummybait-fin/uniswap-tx-builder-mcp server?
io.github.Yummybait-fin/uniswap-tx-builder-mcp is listed in the public MCP registry as io.github.Yummybait-fin/uniswap-tx-builder-mcp. Builds and simulates unsigned Uniswap v3 liquidity-position transactions, keyless, never signs. This page covers its npm package (@yummybait/uniswap-tx-builder-mcp).
Is the io.github.Yummybait-fin/uniswap-tx-builder-mcp server safe to use?
io.github.Yummybait-fin/uniswap-tx-builder-mcp scores 87 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. Its build provenance is signed and verified. 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.Yummybait-fin/uniswap-tx-builder-mcp server expose?
io.github.Yummybait-fin/uniswap-tx-builder-mcp exposes 11 tools: build_collect, build_close, build_mint, build_increase, build_approve, and 6 more. Their descriptions and schemas cost roughly 2,057 tokens of context every time the server is loaded.
Is the io.github.Yummybait-fin/uniswap-tx-builder-mcp server still maintained?
io.github.Yummybait-fin/uniswap-tx-builder-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.Yummybait-fin/uniswap-tx-builder-mcp server under?
io.github.Yummybait-fin/uniswap-tx-builder-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.