SpendNod

io.github.gstack-dsPublished by GitHub account gstack-dsv1.0.2Updated Oct 28, 2026

AI agent spending controls. Set limits, blocklists, and caps. Approve transactions from your phone.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

SpendNod is a remote MCP server for AI agent spending controls: it lets an assistant work within limits, blocklists and caps, with approvals from your phone.

What you can do
  • Apply spending limits, blocklists and caps to an AI agent's activity
  • Keep agent spending within configured boundaries
  • Route transactions for approval from a phone
  • Provide a control layer around agent-initiated payments
When to use it
Worth adding when an AI agent can initiate or approve payments and you want guardrails such as limits, blocklists and caps, plus a human approval step on a phone before money moves.
Requirements
A remote endpoint at api.spendnod.com over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.
Before you install
It governs real spending, so misconfigured limits or caps could allow unintended payments; approvals happen on a phone, so keep that device secure. The description does not detail which transaction data is sent to the service.

Installation

In SourceWeft

  1. Open SpendNod in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.gstack-ds%2Fspendnod/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "spendnod": {
      "type": "http",
      "url": "https://api.spendnod.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

60% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.