Payflowagent
net.payflowagentPublished by payflowagent.netv0.1.0Updated Oct 24, 2026
Free & pay-per-call (x402/USDC) risk & momentum scores for nad.fun tokens on Monad.
Overview
Lets an assistant fetch free and pay-per-call risk and momentum scores for nad.fun tokens on Monad, paying in USDC via x402.
- What you can do
- Provides risk and momentum scores for nad.fun tokens on Monad, with one free tool and additional pay-per-call tools priced in USDC through the x402 payment scheme. Paid calls are settled automatically from a dedicated payer wallet on Base. The manifest does not list individual tool names or parameters.
- When to use it
- Use it when an assistant needs quick risk or momentum signals on nad.fun tokens on Monad, and when you are willing to let it pay small USDC amounts per call for the paid scores. It is not aimed at general market data or other chains.
- Requirements
- Runs as a local npm package (payflowagent-mcp) over stdio, so Node.js is needed. Network access to the PayFlowAgent service is required; PAYFLOWAGENT_API_BASE sets its base URL and defaults to a public endpoint. Paid tools need X402_BUYER_PRIVATE_KEY, the private key of a dedicated Base wallet holding USDC, and optionally X402_BUYER_RPC for the payment RPC endpoint. Without the key only the free tool works. No account or header authentication is declared.
Installation
In SourceWeft
- Open Payflowagent 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.
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
15% 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
Publish an icon in the registry entry.
- 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.