mcpField
P
PayStage Auth Watch

PayStage Auth Watch

Local
paystage.xyzFinance4Updated 2d ago
RepositoryVisit website

About PayStage Auth Watch

PayStage Auth Watch is a read-only MCP server and library for inspecting outstanding token authorizations for a wallet. It lists ERC-20, Permit2, and EIP-3009 authorizations and can evaluate them against a Paystage policy on Base networks.

Key features

  1. 01List outstanding token authorizations
  2. 02Evaluate authorizations against a policy
  3. 03Support ERC-20, Permit2, and EIP-3009
  4. 04Configure wallet, network, tokens, and spenders
  5. 05Base mainnet and Base Sepolia support

Use cases

  1. 01Review a wallet’s outstanding token approvals
  2. 02Check authorizations against a Paystage policy
  3. 03Inspect authorizations on Base or Base Sepolia

MCP support

The MCP server exposes `list_outstanding_auths` and `evaluate_outstanding_auths` tools. Both can accept wallet and network details, authorization filters, policy input, and an RPC URL.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "xyz-paystage-auth-watch": {
      "command": "npx",
      "args": [
        "-y",
        "@paystage/auth-watch"
      ],
      "env": {
        "PAYSTAGE_POLICY_PATH": "<PAYSTAGE_POLICY_PATH>",
        "PAYSTAGE_RPC_URL": "<PAYSTAGE_RPC_URL>"
      }
    }
  }
}
Run commandnpx -y @paystage/auth-watch
Environment variables to set
PAYSTAGE_POLICY_PATHPath to policy.json spending rules
PAYSTAGE_RPC_URLBase RPC URL override

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@paystage/auth-watch0.1.0

Tools

2

Saved tool list · updated 4d ago

ParameterTypeRequiredDescription
policyanyNo
tokensarrayNo
walletstringYes
networkstringNo
rpc_urlstringNo
spendersarrayNo
policy_pathstringNo
eip3009_noncesarrayNo

Details

From the project README

@paystage/auth-watch

Scan and evaluate outstanding token authorizations (ERC-20 allowances, Permit2 allowances, and EIP-3009 nonces) for a wallet against a Paystage policy.

Install

pnpm add @paystage/auth-watch

Library usage

import {
  createRpcClient,
  resolveRpcUrl,
  listOutstandingAuths,
  evaluateOutstandingAuths,
} from "@paystage/auth-watch";
import { loadPolicy } from "@paystage/policy";

const network = "eip155:8453";
const rpc = createRpcClient(resolveRpcUrl(network));
const policy = await loadPolicy("./paystage.policy.json");

const items = await listOutstandingAuths({
  wallet: "0x...",
  network,
  tokens: ["0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"],
  spenders: policy.allowed_spenders ?? policy.allowed_pay_to,
  rpc,
});

const results = evaluateOutstandingAuths(items, policy);

MCP server

node dist/cli.js

Tools:

  • list_outstanding_auths — list outstanding authorizations.
  • evaluate_outstanding_auths — list and evaluate against a policy.

Both accept wallet, optional network, tokens, spenders, policy_path or inline policy, eip3009_nonces, and rpc_url.

Environment

  • PAYSTAGE_RPC_URL — overrides the default RPC URL for the network.

Networks

  • eip155:8453 — Base mainnet (https://mainnet.base.org)
  • eip155:84532 — Base Sepolia (https://sepolia.base.org)

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.