Human authorization gateway for AI agent transactions
{
"mcpServers": {
"io-github-gstack-ds-spendnod": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Human authorization gateway for AI agent transactions
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 5 days ago.
Will it work with my client?
Transport: . Compatibility not confirmed.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for io.github.gstack-ds/spendnod and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A lightweight authorization gateway that sits between AI agents and financial transactions, giving humans control over what their AI agents can spend.
🟡 In Development — Phase 1
AI agents are rapidly gaining the ability to make purchases, book services, and transfer money on behalf of humans. But most people aren't ready to hand their wallets to AI with zero oversight. SpendNod solves this by providing a simple authorization layer — three lines of code for the developer, one swipe to approve for the human.
SpendNod is framework-agnostic and payment-agnostic. It doesn't care if the agent uses LangChain, CrewAI, or a custom framework, and it doesn't care if the payment goes through Stripe, Visa, or crypto. It sits above all of them as the policy and approval layer. Agents call SpendNod first to get permission, then proceed to whatever commerce protocol the merchant supports.
The product is designed around configurable rules — humans set their own risk tolerance (auto-approve under $100, always block gambling, escalate anything over $500) and SpendNod enforces those rules in real-time with sub-second decisions.
# Clone the repo
git clone https://github.com/yourusername/agent-gate.git
cd agent-gate
# Install backend dependencies
cd backend
python -m venv venv
source venv/bin/activate # Windows: venv\Scripts\activate
pip install -r requirements.txt
# Set up environment
cp .env.example .env
# Edit .env with your Supabase credentials
# Run the migration against your Supabase project
# Option A: Via Supabase CLI
supabase db push
# Option B: Copy/paste supabase/migrations/001_initial_schema.sql
# into the Supabase SQL Editor and run it
cd backend
uvicorn app.main:app --reload
# API docs available at http://localhost:8000/docs
cd backend
pytest tests/ -v
from agentgate import AgentGate
gate = AgentGate(api_key="sk-ag-...")
approval = gate.authorize(
action="purchase",
amount=49.99,
vendor="Amazon",
description="Wireless headphones"
)
# Returns: approved, denied, or waits for human approval
POST /v1/authorize with what it wants to doagentgate/
├── backend/
│ ├── app/
│ │ ├── main.py # FastAPI app entry
│ │ ├── config.py # Settings and env vars
│ │ ├── database.py # SQLAlchemy async engine
│ │ ├── mo
... [View full README on GitHub](https://github.com/gstack-ds/agent-gate#readme)