Spawnpay

io.github.RobocularPublished by GitHub account Robocularv0.4.7Updated Oct 24, 2026

Crypto wallets, payments, and referral earnings for AI agents on Base L2

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Local MCP server giving AI agents crypto wallets, payments and referral earnings on the Base L2 network.

What you can do
  • Provides an assistant with crypto wallet, payment and referral-earning capabilities for agents on Base L2.
  • No tool list is published, so the exact operations are not documented here.
  • An API key is used for access and is created automatically on first use if not supplied.
When to use it
Consider it when you want an AI agent to hold or use a crypto wallet, make or receive payments on Base L2, or track referral earnings, and you are comfortable with the associated financial risk.
Requirements
Runs as a local process on the user's machine via the npm package spawnpay-mcp (stdio transport); desktop only, not available as a web executable. Uses the SPAWNPAY_API_KEY environment variable, which is auto-created on first use if not set. Network access to Base L2 is implied.
Before you install
This server involves crypto wallets and payments, so an assistant could move funds or trigger spending; review limits before use. It handles a secret API key (SPAWNPAY_API_KEY) that may be created automatically. No tool list or documentation is published, so the exact actions it can take are unverified.

Installation

In SourceWeft

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

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v0.4.7LatestSep 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.