Near Wallet Manager

io.github.mastrophotPublished by GitHub account mastrophotv0.1.1Updated Oct 24, 2026

MCP server for NEAR wallet creation, balance checks, and transaction signing.

The publisher's own server: Agent Market

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant create NEAR wallets, check account balances, and sign NEAR transactions locally.

What you can do
Exposes three tools for NEAR blockchain wallet work: create_wallet generates an ED25519 keypair or imports an existing private key and returns the public key and implicit account id; check_balance fetches total, locked, and available balances plus key count over NEAR JSON-RPC; sign_transaction signs transfer or function_call payloads and returns the transaction hash, signature, and base64 signed blob.
When to use it
Use it in agent workflows that need to provision a NEAR wallet, inspect an account's balance, or produce signed NEAR transactions deterministically from a local process.
Requirements
Runs as a local stdio process installed from the npm package mcp-near-wallet-manager (Node.js required). Network access to NEAR JSON-RPC is needed for balance checks and signing. No environment variables, headers, or accounts are declared; sign_transaction takes the signer private key as a tool input.
Before you install
create_wallet can return a private key, and sign_transaction accepts signer_private_key as an input, so secrets pass through the assistant and its logs; the README warns to treat returned keys as sensitive, never store private keys in plaintext logs, and use dedicated signer accounts with minimal permissions. Signing produces valid transactions that can move funds, so review actions and deposits before use.

Installation

In SourceWeft

  1. Open Near Wallet Manager in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-near-wallet-manager

MCP server for NEAR wallet operations with three production tools:

  • create_wallet
  • check_balance
  • sign_transaction

Designed for agent workflows where wallets must be provisioned, checked, and used for deterministic signing.

What This Delivers (Job Mapping)

  1. Wallet creation
  • Generates ED25519 keypair or imports existing private key
  • Returns public key + implicit account id
  1. Balance checking
  • Fetches account balance over NEAR JSON-RPC
  • Returns total/locked/available balances and key count
  1. Transaction signing
  • Signs NEAR transaction payloads with transfer/function_call actions
  • Returns transaction hash, signature, and base64 signed transaction blob

Install

bash
npm install -g mcp-near-wallet-manager

MCP Config Example (Claude Desktop)

json
{  "mcpServers": {    "near-wallet-manager": {      "command": "mcp-near-wallet-manager"    }  }}

Tool Inputs

create_wallet

json
{  "network": "testnet",  "include_private_key": true}

check_balance

json
{  "account_id": "near",  "network": "mainnet"}

sign_transaction

json
{  "signer_id": "alice.testnet",  "signer_private_key": "ed25519:...",  "receiver_id": "bob.testnet",  "nonce": "7",  "recent_block_hash": "11111111111111111111111111111111",  "actions": [    {      "type": "transfer",      "deposit_yocto": "1"    }  ]}

Development

bash
npm installnpm run check

Security Notes

  • create_wallet may return a private key: treat as sensitive secret.
  • Never store private keys in plaintext logs.
  • Use dedicated signer accounts and minimal permissions.

Publish Targets

  • npm package: mcp-near-wallet-manager
  • Agent framework integration notes: deliverables/agent-framework-integration.md
  • MCP Registry metadata: server.json

License

MIT

Source: README.md at commit 3ef00d5

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Near integrations