
StablecoinX
io.github.e2xlabsPublished by GitHub account e2xlabsv0.2.0Updated Oct 29, 2026
StablecoinX merchant tools: auth, payments, paymaster, webhooks, floYsh sites and vault settings.
Overview
StablecoinX merchant MCP server that lets an assistant handle auth, payments, paymaster, webhooks, floYsh sites and vault settings from a local process.
- What you can do
- Manage merchant authentication and login sessions
- Create and handle stablecoin payments and paymaster operations
- Configure webhooks for merchant events
- Set up and manage floYsh sites
- Adjust vault settings
- Keep encrypted local state for tokens and session keys
- When to use it
- Use it when you are a StablecoinX merchant and want an assistant to drive payment, paymaster, webhook, site and vault configuration tasks instead of clicking through the dashboard.
- Requirements
- Runs locally over stdio via npx from the npm package, on desktop only. Requires the SCX_STATE_PASSPHRASE secret to encrypt local state; SCX_STATE_DIR optionally sets where that state file lives. The harness endpoint, thirdweb client, origin and login chain are built into the package.
Installation
In SourceWeft
- Open StablecoinX 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
10- v0.2.0LatestOct 29, 2026
- v0.1.13Oct 9, 2026
- v0.1.12Oct 8, 2026
- v0.1.11Oct 2, 2026
- v0.1.10Sep 25, 2026
- v0.1.9Sep 24, 2026
- v0.1.8Sep 19, 2026
- v0.1.7Sep 19, 2026
- v0.1.6Sep 18, 2026
- v0.1.4Sep 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.