Toolkit
One Pinch payments core, wrapped once as an MCP server, plus everything you need to put a responsible AI payments agent in front of it — the agent pack, host recipes, a security guide and a live playground.
A community MCP server over the Pinch Payments API (Australia). 23 tools — 13 read, 10 approval-gated writes — behind stdio and Streamable HTTP, so Claude Desktop, Cursor, LyboAI or any MCP client gets the same capabilities. Every write refuses without confirm:true and returns a preview first; the gate lives in the tool layer, not the prompt.
Payments, payers, subscriptions (with stall detection), cashflow & settlement summaries, payer statements, split-bill status, events — plus a dishonour-diagnosis map that turns Pinch codes into plain English.
Payment links, subscriptions (term / deposit / instalments), splits, refunds, retries, discounts, QR links, plus design_billing, import_payers and one-touch onboard_business. All approve-then-act.
Per-tenant token cache keyed by secret, per-IP rate limiting, body-size caps, output caps, per-call audit logging, a toolsHash manifest on /meta, and a non-root container. BYO keys — no fund aggregation.
stdioStreamable HTTPOAuth2 client-credentialsmetadata attributionTime-Travel sandbox
So any platform can put a safe AI payments agent on Pinch without starting from scratch.
Remi's system prompt, the Design·Do·Ask·Fix playbooks, the dishonour taxonomy, and the guardrail language — byte-identical across every deployment shape.
Drop-in configs for Claude Desktop, LyboAI, and website/app widget embeds — back-office Remi and a restricted customer-facing Front Desk.
SECURITY.md mapped to OWASP GenAI, the SlowMist checklist and Palo Alto's MCP analysis — plus a production hardening roadmap.
A sandbox seed script, a per-coach real-payments seeder, and the live playground to call the tools yourself.
Go and poke at the real thing — no slides.
The toolkit is what we share — the agent pack, recipes, security guide and seeders. The hosted MCP server itself stays proprietary (a gated service, not an open relay), so you run your own or connect to ours with a key.
git clone https://github.com/lybotechgroup/pinch-remi-toolkit cd pinch-remi-toolkit/packages/pinch-mcp cp .env.example .env # add your Pinch sandbox keys npm install && npm run smoke
The agent pack, recipes and security guide live at the repo root; the server is under packages/pinch-mcp.
web.getpinch.com.au → API keys)SETUP.md and SECURITY.md before going liveAccess: replace the clone URL above with the real repo once it's shared. If the repo is private, point this button at a release zip on this site or a request-access form — see the note in SETUP.md.