C

npm:clawvault-mcp-server

https://www.npmjs.com/package/clawvault-mcp-server
75/100 · MCP Trust Grade · checked 2h ago · MCP 0.7.0

What it offers — 30 tools · Finance & Crypto

request_payment

Request a payment transaction through ClawVault. The transaction will be validated against your rules.

check_limits

Check your current spending limits, remaining budget, and session configuration.

get_status

Get ClawVault service status and on-chain feature availability.

list_transactions

List your recent transactions with status and amounts.

swap_tokens

Swap tokens on Solana via dFlow. Best execution across all DEXs. Subject to your spending rules.

get_swap_quote

Get a price quote for a token swap without executing. Use this to check rates.

list_prediction_markets

List available prediction markets on Kalshi via dFlow.

buy_prediction

Buy an outcome (YES or NO) on a prediction market via dFlow. Subject to your spending rules.

sell_prediction

Sell (close/reduce) a prediction market position. Subject to your rules.

redeem_prediction

Redeem winning outcome tokens on a settled prediction market. Market must be determined/finalized.

get_prediction_positions

Get your current prediction market positions and their values.

get_vaults

Get all your vaults across all chains with balances. Use this to check how much USDC/SOL you have available.

get_prediction_wallet

Check if the user has a payment wallet set up, its KYC verification status, and USDC/SOL balance. Required before making prediction trades.

get_payment_wallet_balance

Check USDC balance of payment wallets across all chains (Solana + EVM). Returns balances for each chain where the user has a payment wallet.

fund_payment_wallet

Fund a payment wallet from the main vault. Transfers USDC from the vault to the payment wallet on the specified chain.

withdraw_payment_wallet

Withdraw USDC from a payment wallet back to the main vault (or a custom destination). Use this when the user wants to move funds out of the payment wa

goat_list_actions

List all available GOAT SDK actions (dFlow swaps, SPL transfers, etc.) with their categories and rule requirements.

goat_get_action_rules

Get the current rules configuration for a GOAT action category (swap, transfer, liquidity, prediction, token_ops).

+12 more tools

Spec / packaging20%100
Security (OWASP MCP)30%25
Maintenance / popularity20%100
Tool hygiene15%95
Transparency / provenance15%90

Findings

WARNMCP08 References sensitive file paths / environment secrets.
INFO Static analysis of npm package clawvault-mcp-server@0.7.0 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:clawvault-mcp-server on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:clawvault-mcp-server grade C
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade C · wmcp.sh
[![MCP Trust Grade C](https://wmcp.sh/mcp/grade/npm%3Aclawvault-mcp-server/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Aclawvault-mcp-server)
<a href="https://wmcp.sh/mcp/grade/npm%3Aclawvault-mcp-server"><img src="https://wmcp.sh/mcp/grade/npm%3Aclawvault-mcp-server/badge.svg" alt="MCP Trust Grade C · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.