
Nory X402
io.github.TheMemeBankerPublished by GitHub account TheMemeBankerv1.0.3Updated Oct 24, 2026
Give any AI agent instant payment capabilities via x402 protocol on Solana
Overview
A local MCP server that gives an AI assistant payment capability over the x402 protocol on Solana, using a configured wallet key.
- What you can do
- Lets an assistant make payments through the x402 protocol on Solana, according to the registry description. Connects to a configurable Nory API endpoint that handles the payment flow. Requires a Solana wallet private key supplied to the server so it can authorize payments. No individual tools are listed in the manifest, so the exact operations available are not documented here.
- When to use it
- Consider it when you want an AI assistant to be able to pay for things over x402 on Solana, for example paying for metered API access or other x402-enabled services. It is not useful if you do not want an assistant to spend funds.
- Requirements
- Runs as a local process on the user's machine via the npm package nory-mcp-server (Node.js needed). Requires the NORY_WALLET_KEY environment variable holding a Solana wallet private key, and optionally NORY_API_URL to point at a different Nory API endpoint. Network access to the API endpoint is needed.
Installation
In SourceWeft
- Open Nory X402 in the dashboard and add it to a workspace.
- 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
This repository has no README.
Tools
0Version history
1- v1.0.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.