mcpField
T
Tollary Agent Transaction Guard

Tollary Agent Transaction Guard

Local
github.com/hyKwon13Finance0Updated 8w ago

About Tollary Agent Transaction Guard

Tollary is an experimental local fit-check client and stdio MCP server for autonomous USDC payments on Base Sepolia. It checks an owner-mandated transaction immediately before a customer-owned AWS KMS signer can sign; it does not hold keys or credentials.

Key features

  1. 01Local project fit-check
  2. 02Transaction checks before signing
  3. 03Public metadata inspection
  4. 04Bounded fit-check GitHub Action

Use cases

  1. 01Assess a project for Tollary integration
  2. 02Inspect Tollary public readiness and legal metadata

MCP support

The package includes a stdio MCP server. Tollary's local client and MCP release workflows are included; the hosted service currently supports Base Sepolia testnet payment terms only.

Configuration

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

mcp.json · Universal config
{
"mcpServers": {
"kr-p-e-tollary-agent-transaction-guard": {
"command": "npx",
"args": [
"-y",
"tollary"
]
}
}
}
Run commandnpx -y tollary

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
npmtollary0.1.0

Tools

4

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
originstringNoTollary HTTPS origin.
requestobjectYesPublic unsigned transaction and owner-signed mandate. Never include secrets.

Details

From the project README

Tollary

Experimental beta — Base Sepolia testnet only. No transaction-safety, recipient-identity, legal-compliance, settlement, or loss-prevention guarantee is made. Base Mainnet sales are disabled.

Tollary is a non-custodial Agent Transaction Guard for autonomous Base USDC payments. It checks an exact, owner-mandated transaction immediately before a customer-owned AWS KMS signer can sign it.

This repository contains the open-source local fit-check/MCP client, immutable publication metadata, and guarded npm/MCP release workflows. It does not contain customer keys, payment credentials, hosted-service state, or private backend operations.

Try the client

npx tollary fit-check --project .
npx tollary inspect
npx --yes --package tollary tollary-mcp

The client never accepts a raw wallet or AWS private key. The fit check is local and skips credentials, dependencies, vendor directories, and build output. Inspect mode reads only Tollary's public metadata endpoints.

The hosted service currently exposes Base Sepolia testnet payment terms only. A published package does not mean that Base Mainnet sales are active. Check /api/readiness and /api/legal before every purchase. The npm beta must be selected explicitly with tollary@beta; no latest release is created by the bootstrap workflow.

Repository layout

  • packages/tollary — npm CLI and stdio MCP server
  • distribution/github-action — local, bounded fit-check action
  • .github/workflows — manual, environment-protected npm/MCP publishing
  • scripts — fail-closed publication and namespace validation

The local client is MIT-licensed. Tollary's hosted API, service logic, trademarks, and commercial output are not granted under that license.

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.