Solinkify

com.solinkifyPublished by solinkify.comv0.3.3Updated Oct 24, 2026

Pay for x402 paywalls, datasets, and store checkouts on Solana, behind hard spending caps.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Lets an assistant pay x402 paywalls, datasets and store checkouts on Solana, within hard per-payment and daily spending caps.

What you can do
This local MCP server gives an assistant the ability to settle payments on Solana for x402 paywalls, datasets and store checkouts. Spending is bounded by two hard caps: a maximum for a single payment and a maximum total per UTC day. It can run in owner mode, where a designated owner wallet funds checkouts through its on-chain SpendAuthority while the agent signs but never holds the owner's funds. Discovery and search tools work without a wallet; only the spending tools need the agent keypair.
When to use it
Worth adding when an assistant needs to buy access to paid content, datasets or store checkouts on Solana without manual approval each time, and you want that spending constrained by explicit caps. Not needed if you only want discovery or search, since those tools run without a wallet. Test on devnet first.
Requirements
Runs locally over stdio, installed from the npm package @solinkify/mcp, so Node.js is required; desktop only. No authentication is declared. Optional environment variables: SOLANA_RPC_URL (defaults to public RPC), SOLINKIFY_NETWORK (devnet by default, or mainnet-beta), SOLINKIFY_DAILY_CAP_USD (default 10), SOLINKIFY_MAX_PAYMENT_USD (default 1), SOLINKIFY_OWNER_WALLET, and SOLINKIFY_WALLET_PATH for the agent keypair, which spending tools need.
Before you install
The server spends real funds on Solana. SOLINKIFY_WALLET_PATH points to the agent's JSON keypair, a private key file that must be protected; SOLINKIFY_OWNER_WALLET names the wallet whose on-chain SpendAuthority funds payments. Payments are irreversible once broadcast. Keep SOLINKIFY_NETWORK on devnet until caps and behavior are verified, and set SOLINKIFY_DAILY_CAP_USD and SOLINKIFY_MAX_PAYMENT_USD deliberately rather than relying on defaults.

Installation

In SourceWeft

  1. Open Solinkify 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.

Tools

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

Version history

1
  1. v0.3.3LatestSep 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.