Amrood — INR Payments for AI Agents

io.github.saurabh-karnPublished by GitHub account saurabh-karnv0.4.0Updated Oct 24, 2026

KYC-verified INR wallets for AI agents in India. Payments, escrow, and settlements.

The publisher's own server: Payments Ai Mcp

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Local MCP server giving AI agents KYC-verified INR wallets in India for payments, escrow and settlements via the Amrood API.

What you can do
  • Provides an assistant with access to Amrood's INR wallet infrastructure for AI agents in India.
  • Handles payments, escrow and settlements through the Amrood API.
  • Wallet access is tied to KYC-verified accounts.
  • No individual tools are documented in the supplied material, so exact operations are not described.
When to use it
Consider it when an agent needs to move or hold Indian rupees — paying, holding funds in escrow, or settling — through a KYC-verified wallet rather than a generic payment API.
Requirements
Runs as a local process installed from the PyPI package amrood-mcp (Python). Needs an Amrood agent API key in AMROOD_API_KEY; AMROOD_BASE_URL optionally overrides the API endpoint (defaults to the Amrood API host). Network access to Amrood is required. Desktop only.
Before you install
The server handles real money: payments, escrow and settlements can move funds, so review any action before approving it. It requires a live agent API key (AMROOD_API_KEY) that should be kept secret. Wallet use depends on KYC verification, and account and transaction data is sent to Amrood's API.

Installation

In SourceWeft

  1. Open Amrood — INR Payments for AI Agents 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.0LatestSep 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.

Other Payments integrations