MCP server with 12 tools enabling AI agents (Claude, ChatGPT) to manage Algorand-based subscriptions, including locking funds in vaults and automated payments.
MCP server with 12 tools enabling AI agents (Claude, ChatGPT) to manage Algorand-based subscriptions, including locking funds in vaults and automated payments.
README
Lock ALGO in smart contract vaults you own. An autonomous agent releases payments on billing day. Every transaction is verifiable on Algorand.
Built for AlgoBharat Hack Series 3.0, targeting the Agentic Commerce track, specifically the A2A Autonomous Payments and A2A Agentic Commerce Framework categories.
Most subscription trackers are just spreadsheets with a nicer font. They show you what you spend, but they cannot do anything about it. Unsubscribely puts your subscriptions on-chain. You lock funds in an escrow vault you own, an autonomous agent releases payments on billing day, and every transaction is verifiable on Algorand.
Here is why this is different:
Lock funds in a smart contract vault - your keys, your control, kill switch on everything
Agent releases vaults on billing day every 30 min on Railway, no LLM needed
MCP Server with 12 tools - connect Claude, ChatGPT, or any AI to manage your subscriptions
Telegram bot (@unsublyybot) - cancel by voice/text, get alerts 3 days before renewal
Gmail auto-import - sign in with Google, we detect your subscriptions from receipts
Tinyman DEX swap integration + Gora Oracle ALGO/USD price feeds
Proofs on-chain cancellation proofs - immutable evidence you cancelled
[!NOTE]
The average Indian developer pays for 8-12 SaaS tools in USD, losing 5-7% to forex markup per transaction. Unsubscribely eliminates this with sub-penny on-chain settlement on Algorand.
Per-user vaults (Standard, AgentV2, Time-Lock, Multi-Sig, Dispute, ASA, Cancellation Insurance) are deployed on demand from the dashboard. MainNet singletons are not yet deployed. The app shows clear guards on mainnet for ServiceRegistry-dependent UIs.
[!IMPORTANT]
Security: Smart contracts are compiled with AlgoKit/PuyaPy and tested on TestNet. A formal third-party security audit is planned before any MainNet deployment with real user funds. All contracts are open source for community review.
Architecture
flowchart TD
subgraph USER_LAYER["User Layer"]
USER([?? User])
WALLET[?? Pera / Defly / Lute]
TG[?? Telegram Bot]
CHROME[?? Chrome Extension]
end
subgraph APP_LAYER["Application Layer � Vercel"]
FRONTEND[React Dashboard<br/>14 pages � Vite � Tailwind]
API[Serverless APIs<br/>gmail-scan � mcp-token � x402]
end
subgraph AGENT_LAYER["Agent Layer � Railway"]
AGENT[? Autonomous Agent<br/>14 skills � 30-min cron]
MCP[MCP Server<br/>12 tools � Bearer auth � JSON-RPC]
end
subgraph BLOCKCHAIN["? Algorand TestNet"]
VAULTS[Escrow Vaults<br/>8 contract types � TEAL v11]
REGISTRY[ServiceRegistry<br/>A2A discovery � BoxMap]
PROOFS[Cancellation Proofs<br/>immutable on-chain notes]
ORACLE[Gora Oracle � ALGO/USD]
DEX[Tinyman DEX � ASA swap]
end
subgraph AI_AGENTS["AI Agents"]
CLAUDE([Claude Desktop])
GPT([ChatGPT])
end
subgraph DATA["Data Layer"]
DB[(Supabase<br/>Postgres + RLS)]
end
USER --> WALLET
USER --> TG
USER --> CHROME
WALLET -->|sign + deploy| VAULTS
WALLET --> FRONTEND
FRONTEND --> API
FRONTEND --> DB
API --> DB
TG -->|commands| API
CHROME -->|detect subs| API
AGENT -->|release � kill| VAULTS
AGENT -->|write| PROOFS
AGENT -->|lookup| REGISTRY
AGENT -->|notify| TG
AGENT --> DB
CLAUDE -->|JSON-RPC 2.0| MCP
GPT -->|JSON-RPC 2.0| MCP
MCP --> AGENT
ORACLE -.->|price feed| FRONTEND
DEX -.->|fund vaults| VAULTS
To get a local copy up and running, follow these steps.
[!TIP]
The web app works fully without the agent running. You can browse, add subscriptions, connect a wallet, and create vaults without any Railway or Telegram setup. The agent only adds autonomous vault releases.
Python 3.12 + AlgoKit - only needed if you want to recompile contracts (pre-compiled artifacts are already included)
pip install algokit
[!TIP]
No wallet? The app is fully browsable without connecting Pera. You only need a wallet to deploy escrow vaults or sign transactions.
Installation
Clone the repo
git clone https://github.com/devndesigner6/unsubly.git
cd unsubly
Install dependencies
npm install
Set up environment variables
cp .env.example .env
Open .env.example first - every variable is documented with comments and a generation command. At minimum fill in:
VITE_SUPABASE_URL and VITE_SUPABASE_PUBLISHABLE_KEY from Supabase, Settings, API
SUPABASE_SERVICE_ROLE_KEY from Supabase, Settings, API (service_role key)
CEREBRAS_API_KEY from cloud.cerebras.ai - powers AI Chat page and Telegram bot
AGENT_WALLET_MNEMONIC and VITE_AGENT_WALLET_ADDRESS - generate with the one-liner in .env.example
Run the database schema (first time only)
Go to your Supabase project, SQL Editor
Paste the contents of supabase/migrations/FULL_SCHEMA_SETUP.sql and run it
This file exists at the root of the migrations folder and creates all tables, RLS policies, and indexes in one shot
Start the dev server
npm run dev
App runs at http://localhost:5000
Mac users: port 5000 conflicts with AirPlay Receiver. Either disable AirPlay (System Settings, AirDrop & Handoff) or change the port in vite.config.ts and package.json scripts to 5001.
Run the test suite
npx vitest run # frontend unit tests
cd smart_contracts && pytest tests/ # smart contract tests
Production build and serve
npm run build
npm run start
Running the real OpenClaw agent locally
The production agent is a real OpenClaw Gateway workspace, separate from the web app. OpenClaw owns the runtime and cron schedule; the existing Unsubscribely vault code is exposed through the unsubscribely_vault_monitor workspace skill.
cd agents/openclaw
npm install
npm run start
Create agents/openclaw/.env or export these values before starting:
npm run start writes an OpenClaw config, seeds a recurring OpenClaw cron job named Unsubscribely vault monitor, and starts openclaw gateway run. The cron job runs every 30 minutes and tells OpenClaw to execute npm run monitor:vaults from this workspace.
For a direct deterministic check without the Gateway, run:
npm run monitor:vaults
Optional: recompile smart contracts or deploy to testnet
Recompile contracts (pre-compiled artifacts are already included):
1. Lock - Add a subscription and deploy an escrow vault from the dashboard. Choose from 7 vault types: Standard, AgentV2, Time-Lock, Multi-Sig, Dispute, ASA, or Cancellation Insurance. Your ALGO sits in a contract you own.
2. Release - OpenClaw checks every 30 minutes. When a billing date hits, it verifies the recipient against the on-chain ServiceRegistry, checks your spending guardrails, and calls release() on the contract. Funds go directly on-chain. You get a Telegram notification with the transaction ID.
3. Prove - Mint an ARC-3 NFT receipt after each release. AgentEscrowVaultV2 also writes an immutable BillingRecord into Box Storage per cycle, giving you a full on-chain billing history.
Phase 1current - Free for users. Revenue from x402 micro-payments: external AI agents pay 0.001 ALGO per API call to access subscription data. No API keys, no subscriptions needed. Payment IS the credential.
Phase 2post-audit - Mainnet launch. Premium MCP access ($5/mo for write+admin scope). ServiceRegistry listing fee (one-time ALGO payment for service providers to publish).
Phase 3 - B2B vault infrastructure. Companies use escrow contracts for employee subscription procurement. Agent handles vendor payments autonomously.
Target users: Indian developers and freelancers (25-35) managing 8-12 SaaS tools (Notion, GitHub, Cursor, Figma) totaling $50-150/month in USD, losing 5-7% to forex fees per transaction.
Why Algorand:3.3s finality � sub-penny fees � ARC-4 ABI for clean contract interfaces � Box Storage for on-chain history � instant settlement without L2 complexity.
