aptos-wallet-mcp

Created By
longciphera year ago
MCP server for aptos wallet
Overview

what is aptos-wallet-mcp?

aptos-wallet-mcp is a server designed for managing Aptos Wallet functionalities, allowing users to interact with the Aptos blockchain.

how to use aptos-wallet-mcp?

To use aptos-wallet-mcp, clone the repository from GitHub, build the project using Cargo, and run the server with the provided configuration file.

key features of aptos-wallet-mcp?

  • Get balance of an Aptos account
  • Transfer APT between accounts
  • Check the status of transactions
  • Generate new Aptos accounts
  • Fund accounts using the devnet faucet

use cases of aptos-wallet-mcp?

  1. Managing cryptocurrency balances in Aptos accounts.
  2. Facilitating APT transfers for users.
  3. Monitoring transaction statuses for better user experience.
  4. Creating and funding new Aptos accounts for development purposes.

FAQ from aptos-wallet-mcp?

  • What programming language is aptos-wallet-mcp written in?

aptos-wallet-mcp is written in Rust.

  • Is there a license for this project?

Yes, it is licensed under the Apache-2.0 license.

  • How can I contribute to the project?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
longcipher
Star
0
Language
Rust
License
Apache-2.0 license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

7 hours ago