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.mastrophot/near-wallet-manager

NPM · MCP-NEAR-WALLET-MANAGER · SCANNED SEP 25

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

0 this week 77 Trust /100
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 Security97
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 148 of 154 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 148 of 154 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 206 tokens (~68/item across 3 items; 3 tools + 0 resources), lean.Pass
  • 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 Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 31% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
Install

How do I install the io.github.mastrophot/near-wallet-manager MCP server?

io.github.mastrophot/near-wallet-manager runs locally as an npm package, launched with npx -y mcp-near-wallet-manager. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-near-wallet-manager

# add to Claude Code
claude mcp add mastrophot-near-wallet-manager -- npx -y mcp-near-wallet-manager
// .cursor/mcp.json
{
  "mcpServers": {
    "mastrophot-near-wallet-manager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-near-wallet-manager"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mastrophot-near-wallet-manager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-near-wallet-manager"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mastrophot-near-wallet-manager -- npx -y mcp-near-wallet-manager
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mastrophot-near-wallet-manager": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-near-wallet-manager"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mastrophot-near-wallet-manager --command npx --arg -y --arg mcp-near-wallet-manager
# ~/.hermes/config.yaml
mcp_servers:
  mastrophot-near-wallet-manager:
    command: "npx"
    args: ["-y", "mcp-near-wallet-manager"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mastrophot-near-wallet-manager": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-near-wallet-manager"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mastrophot-near-wallet-manager -t stdio -c npx -a -y mcp-near-wallet-manager
// mcp.json
{
  "mcpServers": {
    "mastrophot-near-wallet-manager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-near-wallet-manager"
      ]
    }
  }
}
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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 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.

  • 23 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 22 Sept 26 0
    • Stability: 0.97 → pass security
  • 21 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.

  • 19 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.

  • 17 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.

  • 16 Sept 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 25 Sept 2026 · Analysed npm/mcp-near-wallet-manager@0.1.1

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 →

Dependencies 148 packages
Packages resolved 148
Stale 62
No linked repository 1
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~206 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
check_balance ~50

Check NEAR account balance and key stats via JSON-RPC.

NameTypeReqDescription
account_idstringyes–
networkstring––
rpc_urlstring–Required only when network=custom

No output schema declared.

No examples provided.

create_wallet ~74

Create or import a NEAR wallet (keypair) and return implicit account info.

NameTypeReqDescription
account_idstring–Optional named/implicit account id to associate
include_private_keyboolean––
networkstring––
private_keystring–Optional: import existing ed25519 private key

No output schema declared.

No examples provided.

sign_transaction ~82

Sign a NEAR transaction payload (transfer/function_call actions) with an ED25519 private key.

NameTypeReqDescription
actionsarrayyes–
nonce–yes–
receiver_idstringyes–
recent_block_hashstringyesBase58 block hash (32-byte decoded)
signer_idstringyes–
signer_private_keystringyes–

No output schema declared.

No examples provided.

Common questions

What is the io.github.mastrophot/near-wallet-manager MCP server?

io.github.mastrophot/near-wallet-manager is an MCP server listed in the public MCP registry as io.github.mastrophot/near-wallet-manager. MCP server for NEAR wallet creation, balance checks, and transaction signing. This page covers its npm package (mcp-near-wallet-manager).

Is the io.github.mastrophot/near-wallet-manager MCP server safe to use?

io.github.mastrophot/near-wallet-manager scores 77 out of 100 on VerifyMCP. 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.mastrophot/near-wallet-manager MCP server expose?

io.github.mastrophot/near-wallet-manager exposes 3 tools: create_wallet, check_balance, sign_transaction. Their descriptions and schemas cost roughly 206 tokens of context every time the server is loaded.

Is the io.github.mastrophot/near-wallet-manager MCP server still maintained?

io.github.mastrophot/near-wallet-manager is still listed as active in the MCP registry. We last reached this channel on 25 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.mastrophot/near-wallet-manager MCP server under?

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