Skip to main content
Glama
Sign In
Allow

Allow

by bigrceo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Allow

Give your agent a wallet. Claude, ChatGPT or any MCP client gets a Solana wallet with an allowance. It pays APIs over x402, trades any Solana token through Jupiter, and every action lands in a public registry anchored on Solana.

npm i -g https://useallow.xyz/downloads/allow-kit-0.1.0.tgz && allow init          # wallet + allowance in ~/.allow
allow serve         # site, dashboard, /verify on :4340
claude mcp add allow -- npx -y https://useallow.xyz/downloads/allow-kit-0.1.0.tgz mcp

Part

Where

MCP tools: allow_wallet allow_budget allow_pay allow_quote allow_swap allow_token allow_history

mcp/tools.mjs (stdio mcp/server.mjs, HTTP /mcp/<key>)

Wallet + allowance (caps, pay list, token list, expiry, revoke, sweep)

lib/wallet.mjs, lib/core.mjs#guard

x402 client and seller (Solana, exact scheme, USDC with seller-paid fee or SOL)

lib/x402.mjs, demo endpoints /x402/price, /x402/sol

Trading (Jupiter, ported from SAY)

lib/jupiter.mjs, lib/core.mjs#quote/swap

Registry: hash chain, ed25519, Merkle root in SPL Memo (from HUSH)

lib/registry.mjs, lib/merkle.mjs, /verify

CLI

bin/allow.mjs

Brand (name, colors, logo)

brand.mjs, the only place

Modes. ALLOW_CLUSTER=localnet|devnet|mainnet (default devnet). Prices always come from Jupiter mainnet. Swaps are simulated (paper fill at the fresh quote, marked simulated in the registry) unless ALLOW_CLUSTER=mainnet and ALLOW_LIVE=1. x402 payments and registry anchors are real transactions on the chosen cluster.

Demo. node scripts/demo.mjs BONK pays the x402 price API, buys, sells half, prints the registry.

Every claim, mapped to code and to a way to check it: CLAIMS.md.

Install for Claude and ChatGPT: docs/INSTALL.md. Security model: SECURITY.md.

Deploy. npm run pack writes web/downloads/allow-kit-<version>.tgz, which the site serves for the one-line install.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessSyncing

Resources

Related MCP Connectors

Related MCP Servers

  • onchain-agent-wallets

    nirholas
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server that gives AI agents a Solana wallet with a capped, revocable token allowance from a user-owned vault, enforced on-chain by SPL Token delegations plus local guardrails, without exposing the owner's private key.
    102 npm
    9
    Apache 2.0
  • @vapi-network/mcp

    @vapi-network/mcpofficial

    vAPI-Network
    A
    license
    Not graded
    quality
    B
    maintenance
    Lets MCP clients discover x402 APIs, pay for calls from a local non-custodial wallet, and inspect balances and payment receipts.
    11
    Apache 2.0

  • stellar-x402-mcp

    DarkLvrd
    A
    license
    Not graded
    quality
    B
    maintenance
    Gives an AI agent a Stellar wallet for x402 payments whose spending budget is installed and enforced on-chain by a Soroban smart contract, so overspending is refused by the contract even if the agent process is compromised, replaced, or restarted. Budgets are declared as scoped, non-rounding data (e.g. 5 USDC per rolling day) that the agent can spend against but cannot alter or redirect.
    MIT

  • presign-guard-wallet-mcp

    Fizzl13
    A
    license
    A
    quality
    A
    maintenance
    A wallet for AI agents with spending limits: pays x402 and MPP APIs in USDC (Base, Solana, Algorand) and RLUSD (XRP Ledger), checks every payment with presign-guard first, and asks for approval on your phone above your limits. Source in the wallet-mcp folder; npm: presign-guard-wallet-mcp.
    7
    MIT