PaidPilot Invoice Tools
REMOTE · API.PAIDPILOT.IO
Invoice tools: reminders, late fees, terms, timesheets and a receivables health report (x402).
Available components
Last scanned (3 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1793 tokens (~256/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.paidpilot.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=paidpilot.io | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2dfe058b0d4319980ea1170c3597887c |
| SANs: paidpilot.io, api.paidpilot.io, *.api.paidpilot.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.paidpilot.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| paidpilot.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.paidpilot.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.paidpilot.io/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
invoice_from_timesheet ~293
Turn time entries (hours x rate, with optional rounding, grouping by task and expenses) into a validated invoice JSON with totals, ready for POST /v1/invoice.pdf. Use validate_invoice (free) instead if you already have an invoice. Pure calculation: no network request, nothing is sent or stored. Costs $0.02 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input returns an error and is not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | object | yes | – |
| currency | string | – | – |
| default_rate | number | – | Hourly rate for entries without their own rate |
| discount | number | – | – |
| due_date | string | – | YYYY-MM-DD; or give terms instead |
| entries | array | yes | – |
| expenses | array | – | Reimbursable expenses, one line each |
| group_by | string | – | entry = one line per entry; description = merge entries with the same description and rate |
| invoice_number | string | yes | – |
| issue_date | string | yes | – |
| notes | string | – | – |
| payment_instructions | string | – | – |
| rounding | object | – | – |
| seller | object | yes | – |
| tax_rate | number | – | – |
| terms | string | – | e.g. "Net 15"; sets due_date from issue_date (early-pay discounts are not applied to the invoice) |
No output schema declared.
No examples provided.
late_fee_calc ~327
Calculate the late fee on one overdue invoice: flat fee, monthly % or annual %, simple or compounding, with optional grace days. Returns days late, the fee, the new total and a line to paste on the invoice. Use payment_terms_check instead to work out when an invoice is due. Not legal advice; it does not look up state caps. Pure calculation: no network request, nothing is sent or stored. Costs $0.01 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input returns an error and is not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Unpaid invoice amount |
| as_of | string | – | Date paid, or the date to calculate to, YYYY-MM-DD (default: today, UTC) |
| compounding | boolean | – | false = simple interest (default); true = compounds (monthly: per 30 days; annual: daily) |
| currency | string | – | ISO-4217, default USD |
| due_date | string | yes | Invoice due date, YYYY-MM-DD |
| fee_type | string | yes | flat = one fixed fee; monthly_percent e.g. 1.5; annual_percent e.g. 18 |
| flat_fee | number | – | Flat fee; required for fee_type=flat, optional one-time add-on otherwise |
| grace_days | integer | – | Days after the due date before any fee applies |
| rate_percent | number | – | Rate for monthly_percent / annual_percent |
| state | string | – | US state (2-letter) for the legal note |
No output schema declared.
No examples provided.
payment_reminder_draft ~298
Draft a payment reminder email for one unpaid invoice in a friendly, firm or final-notice tone. Returns a subject, plain-text body, days overdue and a suggested next step. Use late_fee_calc first if you want the fee amount quoted in the email. Draft only: nothing is sent. Pure calculation: no network request, nothing is sent or stored. Costs $0.01 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input returns an error and is not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Amount due |
| as_of | string | – | Today's date for the days-overdue count, YYYY-MM-DD (default: today, UTC) |
| client_name | string | – | Client's name for the greeting |
| currency | string | – | ISO-4217, default USD |
| due_date | string | – | YYYY-MM-DD |
| final_deadline_days | integer | – | Final notice: days the client has to pay |
| from_name | string | yes | Your name or business, used in the sign-off |
| invoice_number | string | – | – |
| late_fee_terms | string | – | Your agreed late-fee terms, e.g. "1.5% per month"; mentioned in the final notice only |
| payment_link | string | – | – |
| tone | string | yes | "friendly" (alias "polite"), "firm", or "final" |
No output schema declared.
No examples provided.
payment_terms_check ~233
Work out the due date and status for payment terms such as Net 30, 2/10 Net 30, Due on receipt, EOM or Net 30 EOM. Returns the early-payment discount amount and deadline, the annualized cost of skipping the discount, and suggested reminder dates. Use late_fee_calc once the invoice is overdue. Pure calculation: no network request, nothing is sent or stored. Costs $0.01 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input returns an error and is not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Invoice total (optional; enables the discount math) |
| as_of | string | – | Date to compute status for, YYYY-MM-DD (default: today, UTC) |
| currency | string | – | ISO-4217, default USD |
| invoice_date | string | yes | Invoice date, YYYY-MM-DD |
| terms | string | yes | Payment terms, e.g. "Net 30", "2/10 Net 30", "Due on receipt", "EOM", "Net 30 EOM" |
No output schema declared.
No examples provided.
pricing ~45
Free. Return the price of every paid tool and of the HTTP invoice PDF route, the payment network (Base) and the receiving address. No input, no network request, no payment.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
receivables_health_report ~353
Grade the health of a business's accounts receivable from its invoice list. Send a CSV export (QuickBooks, Xero, FreshBooks, Wave, Stripe or any CSV with customer and amount columns; columns are auto-detected) or JSON rows, up to 1000 invoices. Returns an A-F grade and 0-100 score with reasons, aging buckets (current, 1-30, 31-60, 61-90, 90+ days), overdue %, weighted days outstanding, DSO, average days to pay, customer concentration, a collection priority list with the next action per overdue invoice (pointing to payment_reminder_draft and late_fee_calc), and recommendations. Use it for a monthly AR review or before chasing payments. Not accounting or legal advice. Pure calculation: no network request, nothing is sent or stored. Costs $1 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input returns an error and is not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Report date, default today (UTC) |
| csv | string | – | CSV export (QuickBooks, Xero, FreshBooks, Wave, Stripe or your own). Header row required. Recognized columns: invoice number, customer, amount/total, amount paid, balance/open balance, invoice date,… |
| currency | string | – | – |
| default_terms | string | – | Used when a row has no due date and no terms |
| invoices | array | – | Or JSON rows instead of CSV |
| revenue_window_days | integer | – | Window for DSO: invoiced amount in the last N days |
No output schema declared.
No examples provided.
validate_invoice ~101
Free. Validate an invoice JSON (the body for POST /v1/invoice.pdf, or the output of invoice_from_timesheet) and return computed subtotal, discount, tax and total, or a list of field errors. Same checks as the paid PDF route. Offline, no payment.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | object | yes | Invoice object: from, to, number, issue_date, currency, line_items[{description, quantity, unit_price}], optional tax and discount |
No output schema declared.
No examples provided.
How do I install the PaidPilot Invoice Tools MCP server?
PaidPilot Invoice Tools is a hosted endpoint at https://api.paidpilot.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.paidpilot.io
claude mcp add --transport http io-paidpilot-api-invoice-tools 'https://api.paidpilot.io/mcp'
What is the PaidPilot Invoice Tools MCP server?
PaidPilot Invoice Tools is an MCP server listed in the public MCP registry as io.paidpilot.api/invoice-tools. Invoice tools: reminders, late fees, terms, timesheets and a receivables health report (x402). This page covers its hosted endpoint (https://api.paidpilot.io/mcp).
Is the PaidPilot Invoice Tools MCP server safe to use?
PaidPilot Invoice Tools scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PaidPilot Invoice Tools MCP server expose?
PaidPilot Invoice Tools exposes 7 tools: pricing, validate_invoice, payment_reminder_draft, late_fee_calc, payment_terms_check, and 2 more. Their descriptions and schemas cost roughly 1,650 tokens of context every time the server is loaded.
Does the PaidPilot Invoice Tools MCP server require authentication?
No. We connected to PaidPilot Invoice Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PaidPilot Invoice Tools MCP server still maintained?
PaidPilot Invoice Tools is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.