Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.WarTech9/clawswap

NPM · @CLAWSWAP/MCP-SERVER

Cross-chain swaps between Solana and Base for AI agents paid for via via x402 micropayments.

−2 this week 74 Trust /100

Last scanned (7 hours ago)

Scores higher than 49% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security82
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 32 of 246 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 625 tokens (~208/item across 3 items; 3 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 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; "clawswap_bridge" 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 4 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
Changelog

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.

  • 4 Nov 26 −2
    • Stability: pass → 0.83 functional
  • 29 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 22 Oct 26 0
    • Stability: 0.97 → pass security
  • 21 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +3
    • Stability: 0.80 → pass security
  • 16 Oct 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

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 5 Nov 2026 · Analysed npm/@clawswap/mcp-server@0.1.5

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 246 packages
Packages resolved 246
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~371 tokens

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 →

Tool Tokens
clawswap_bridge ~187

Send, transfer, swap, or bridge tokens cross-chain between Solana and Base. Handles quoting, payment, signing, and submission automatically. Use this to move USDC, USDT, SOL, ETH, or WETH between chains.

NameTypeReqDescription
amountstringyesHuman-readable amount to bridge, e.g. '100', '0.5'. NOT base units.
destinationTokenstring–Destination token symbol. Defaults to same token or USDC.
fromstringyesSource chain
recipientstringyesDestination wallet address to receive the bridged tokens.
slippagenumber–Slippage tolerance 0-1. Default 0.01 (1%).
tostringyesDestination chain
tokenstringyesToken symbol on the source chain: USDC, USDT, SOL, ETH, WETH

No output schema declared.

No examples provided.

clawswap_quote ~142

Get a price quote for a cross-chain transfer between Solana and Base. Shows estimated output amount, fees, and time. Free, no payment required. Use before bridging to preview costs.

NameTypeReqDescription
amountstringyesHuman-readable amount, e.g. '100', '0.5'
destinationTokenstring–Destination token symbol. Defaults to same token or USDC.
fromstringyesSource chain
slippagenumber–Slippage tolerance 0-1. Default 0.01 (1%).
tostringyesDestination chain
tokenstringyesToken symbol on the source chain

No output schema declared.

No examples provided.

clawswap_status ~42

Check the status of a previously initiated bridge using the requestId from clawswap_bridge.

NameTypeReqDescription
requestIdstringyesThe requestId returned by clawswap_bridge

No output schema declared.

No examples provided.

Install

How do I install the io.github.WarTech9/clawswap MCP server?

io.github.WarTech9/clawswap runs locally as an npm package, launched with npx -y @clawswap/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 · @clawswap/mcp-server

# add to Claude Code
claude mcp add wartech9-clawswap -- npx -y @clawswap/mcp-server
Common questions

What is the io.github.WarTech9/clawswap MCP server?

io.github.WarTech9/clawswap is an MCP server listed in the public MCP registry as io.github.WarTech9/clawswap. Cross-chain swaps between Solana and Base for AI agents paid for via via x402 micropayments. This page covers its npm package (@clawswap/mcp-server).

Is the io.github.WarTech9/clawswap MCP server safe to use?

io.github.WarTech9/clawswap scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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.WarTech9/clawswap MCP server expose?

io.github.WarTech9/clawswap exposes 3 tools: clawswap_bridge, clawswap_quote, clawswap_status. Their descriptions and schemas cost roughly 371 tokens of context every time the server is loaded.

Is the io.github.WarTech9/clawswap MCP server still maintained?

io.github.WarTech9/clawswap is still listed as active in the MCP registry. We last reached this channel on 5 November 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.WarTech9/clawswap MCP server under?

io.github.WarTech9/clawswap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.