Pink Agentic AI Payments (by PinkWallet): lets Claude, ChatGPT, Cursor pay vendor invoices within company spending rules (budgets, caps, allow-lists, human approval). Sandbox preview, test money.
RevExOS is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Quote-to-cash tools: parse invoices and POs, match POs to invoices, collection emails, billing math.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http revexos-mcp https://revexos.com/api/mcp
# 2 — ask your agent for something these tools do
# generate_ar_collection_email, parse_invoice, parse_purchase_order and 5 more
RevExOS costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http revexos-mcp https://revexos.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Generate a ready-to-send accounts receivable follow-up email for an overdue or upcoming invoice, tuned by how overdue it is (1-6) and whether to protect a long-term relationship. Requires an email address to attribute the request; RevExOS sends occasional updates about new free AR/collections tools to it, never spam.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | The requester's email address, required to generate output. | |
| name | string | no | The requester's name. |
| company | string | no | The requester's company. |
| stage | integer | yes | How overdue the invoice is: 1=pre-due (3 days before), 2=due today, 3=1-7 days late, 4=8-14 days late, 5=15-30 days late (firm), 6=31+ days late (final notice). |
| relationship | string | yes | "standard" for a generic escalation tone, "vip" for a long-term/high-value customer where the tone should stay softer. |
| custName | string | yes | The customer/contact name to address the email to. |
| invoiceNum | string | yes | The invoice number, e.g. "INV-1042". |
| amountStr | string | yes | The formatted amount due including currency symbol, e.g. "$4,500". |
| dueDateStr | string | yes | The formatted due date, e.g. "Sep 12, 2026". |
| daysOverdue | string | no | How many days overdue the invoice is, as a string. Ignored for stages 1-3. |
| senderName | string | no | The sender's own name, used in the closing signature. |
| senderCompany | string | no | The sender's company, used in the closing signature. |
| paymentLink | string | no | An optional payment link to include in the email body. |
Extract structured data from an invoice (PDF, PNG, JPEG, WebP or GIF, up to 10MB) at a public https URL or attached in ChatGPT: invoice number, dates, PO number, vendor and customer, currency, payment terms, subtotal, tax, total, and every line item. Also checks whether the line items add up to the subtotal and the subtotal plus tax to the total. A URL must download the file directly without a log
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_url | string | no | Public https URL of the invoice file (PDF or image). |
| file | object | no | The invoice file the user attached in ChatGPT. Use this or the URL field, not both. |
| string | yes | The requester's email address, required to parse. | |
| name | string | no | The requester's name. |
| company | string | no | The requester's company. |
Extract structured data from a purchase order (PDF or image, up to 10MB) at a public https URL or attached in ChatGPT: PO number, dates, buyer and vendor, currency, payment terms, totals and every line item with SKU, quantity and unit price. A URL must download the file directly without a login. The file is not stored. Requires an email address; 5 per email per day. Extracted values are data copie
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_url | string | no | Public https URL of the purchase order file (PDF or image). |
| file | object | no | The purchase order file the user attached in ChatGPT. Use this or the URL field, not both. |
| string | yes | The requester's email address, required. RevExOS sends occasional updates about new free AP/AR tools to it, never spam. | |
| name | string | no | The requester's name. |
| company | string | no | The requester's company. |
Compare a purchase order with the invoice billed against it (the PO and invoice legs of a three-way match). Each file (PDF or image) is a public https URL or a file attached in ChatGPT. Returns both extracted documents plus header checks (PO number, buyer, vendor, currency) and line-by-line checks: match, quantity differs, unit price differs, on PO but missing from the invoice, or on the invoice b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| po_url | string | no | Public https URL of the purchase order file. |
| invoice_url | string | no | Public https URL of the invoice file. |
| po_file | object | no | The purchase order file the user attached in ChatGPT. Use this or the URL field, not both. |
| invoice_file | object | no | The invoice file the user attached in ChatGPT. Use this or the URL field, not both. |
| string | yes | The requester's email address, required. RevExOS sends occasional updates about new free AP/AR tools to it, never spam. | |
| name | string | no | The requester's name. |
| company | string | no | The requester's company. |
Prorate a mid-period plan change (upgrade, downgrade, seat change): credit for the unused part of the old plan, charge for the rest of the period on the new plan, and the net amount. Method "months" (default) counts every whole month of the period equally and splits only the partial month by its own days; "days" spreads the price over every day of the period (Stripe default). Monthly plans give th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cycle | string | yes | Billing period length. |
| period_start | string | yes | Start date of the current billing period, YYYY-MM-DD. |
| change_date | string | yes | Date the change takes effect, YYYY-MM-DD. Must fall inside the period. |
| old_price | number | yes | Price per unit of the current plan for one full period. |
| new_price | number | yes | Price per unit of the new plan for one full period. |
| old_quantity | number | no | Units/seats on the current plan. Default 1. |
| new_quantity | number | no | Units/seats on the new plan. Default 1. |
| method | string | no | "months" (default) or "days". |
Build a month-by-month revenue recognition schedule (ASC 606 / IFRS 15 style, single performance obligation) with billed, recognized, deferred revenue and unbilled revenue per month. Models: "subscription" (equal per full month, partial first/last month by its own days, billed upfront/annual/quarterly/monthly in advance), "milestone" (recognized when each milestone is delivered, optional deposit),
| Parameter | Type | Required | Notes |
|---|---|---|---|
| model | string | yes | — |
| start_date | string | yes | Contract start date, YYYY-MM-DD. |
| total | number | no | subscription: total contract value. |
| term_months | integer | no | subscription (max 120) or usage (max 60): term in months. |
| billing | string | no | subscription: billing frequency, in advance. Default upfront. |
| deposit_pct | number | no | milestone: % of the total invoiced at the start. Default 0. |
| milestones | array | no | milestone: delivery date and value of each milestone. |
| commitment | number | no | usage: prepaid commitment amount, invoiced at the start. |
| first_month_usage | number | no | usage: usage value in the first month. |
| monthly_growth_pct | number | no | usage: month-over-month usage growth in %. Default 0. |
Simple interest on an overdue invoice: amount x annual rate x days overdue / 365, plus a flat late fee. Mode "annual" (contract rate per year), "monthly" (rate per month, converted x12), or "uk" (UK Late Payment of Commercial Debts Act: 8% + Bank of England base rate, plus fixed compensation of GBP 40/70/100 by debt size). Same math as revexos.com/late-payment-interest-calculator. Whether interest
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount | number | yes | Invoice amount outstanding. |
| due_date | string | yes | Invoice due date, YYYY-MM-DD. |
| paid_date | string | no | Payment date or the date to calculate to, YYYY-MM-DD. Default today. |
| mode | string | yes | — |
| annual_rate_pct | number | no | annual mode: rate per year in %. |
| monthly_rate_pct | number | no | monthly mode: rate per month in %, e.g. 1.5. |
| uk_base_rate_pct | number | no | uk mode: Bank of England base rate in % on the relevant reference date (30 June or 31 December before the debt became overdue). |
| flat_fee | number | no | annual/monthly modes: flat late fee to add. Default 0. |
Work out an invoice due date from its payment terms (due on receipt, Net 7/10/14/15/30/45/60/90, EOM, Net 30 EOM, or a custom number of days), and the date the cash actually lands after a late payment and the payment method clearing time (card 0, wire 1, ACH 2, check 7 business days). Weekend dates roll to Monday by default. Same math as revexos.com/invoice-due-date-calculator.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice_date | string | yes | Invoice date, YYYY-MM-DD. |
| terms | string | yes | — |
| custom_days | integer | no | custom terms: days after the invoice date. |
| days_late | integer | no | How many days after the due date the client usually pays. Default 0. |
| payment_method | string | no | Default ach. |
| roll_weekends | boolean | no | Move weekend dates to Monday. Default true. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install RevExOS or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish RevExOS can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.