pingLABSCO SUMMARY
The creditor desk, driven in plain English.
Account creation, status changes and the four standard reports sit behind a single API key, and the plan on that key decides how far a conversation can go - so a read-only key and a full one are the same integration with different reach.
What it is
A FastMCP server exposing the creditor-facing side of the FixPayment portal. Every call carries an API key, and the plan that key maps to - basic, reports or full - decides which of the 13 tools answer - 5 on basic, 9 on reports, all 13 on full.
What you get
- New creditor accounts created one at a time or in bulk
- An account's status moved
- A document attached to an account
- A payload checked before you commit it
- Account summaries and a basic account listing
- Four reports - accounts, payments, settlements and performance
- The plan your key is on, read back
Requirements
A FixPayment API key, passed as an argument on every tool call. The key maps to one plan and the plan gates the tools: basic covers the summary and listing calls, reports adds the four report tools, full adds account creation and status changes. If a tool will not answer, read the plan back first. The endpoint is https://fixpayment.org:8000/mcp/ (the README still prints http://, which that port now rejects); self-hosting instead also needs PostgreSQL, the five FIXPAYMENT_DB_ variables and an upload directory.
Setup effort
Add the hosted endpoint plus a key — paste it into your client, then supply credentials
USE CASES
01
Onboarding a batch of new accounts at once
Validate the payload first, then create the whole batch in one call rather than one form at a time.
02
Answering where the money landed last month
Payments and settlements are separate reports, so the received and the settled figures do not get conflated.
03
Moving an account along after a customer call
Read the summary, change the status, and the portal reflects it immediately.
04
Filing paperwork against the right account
Attach the document to the account by id instead of uploading it through the portal.
05
Finding out why a tool will not answer
Read the plan your key is on - basic, reports or full - and it names what that key can reach.
06
Reviewing the book before a meeting
Pull the account and performance reports, and list the accounts behind them.
13 tools
Listed in project docs. Your client may show a different list.
get_plan_infoget_account_summarylist_accounts_basicvalidate_account_payloadaccounts_reportpayments_reportsettlements_reportperformance_reportcreate_accountbulk_create_accountsupdate_account_statusadd_account_documentBEFORE YOU INSTALL
What to know first
Tools you get
13 tools named in the project's documentation. Your API key's plan decides the set: basic exposes 5 tools, reports 9, and full all 13.
INSTALLATION
Connect your client
Paste it into your client, then supply credentials.
Server setup
Setup
TERMINAL
# 1. Clone & install dependencies
git clone https://github.com/prmail/fixpayment_mcp.git
cd fixpayment_mcp
pip install -r requirements.txt
# 2. Configure credentials
cp .env.example .env
# Edit .env and set FIXPAYMENT_DB_* variables
# 3. Run the server
python -m mcp.server
# or via FastMCP CLI:
fastmcp run mcp/server.py:mcpHosted endpoint
ENDPOINT URL
https://fixpayment.org:8000/mcp/Add this hosted endpoint to your MCP client using the credentials listed under Requirements.
