PivotBank
REMOTE · PIVOTBANK.APP
Convert bank statement PDFs to Excel, CSV, OFX or QBO, every row checked against the balances.
Available components
Last scanned (3 hours ago)
Scores higher than 93% 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 Security80
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 553 tokens (~138/item across 4 items; 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 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 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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://pivotbank.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pivotbank.app | CN=YE2,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 61dc03c4f19a2257e3aa856f8f99dec6f05 |
| SANs: *.pivotbank.app, pivotbank.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pivotbank.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| pivotbank.app. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | base-uri 'self'; object-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pivotbank.app/mcp | Verified | 200 | |
| http (plaintext) | http://pivotbank.app/mcp | HTTPS enforced | 301 | https://pivotbank.app/mcp |
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 →
check_statement_balances Check that a bank statement adds up ~124
Use this when the user asks whether a bank statement is complete, correct or genuine, or why its numbers do not add up. Reads the PDF and checks every row against the statement's own running balances: opening plus money in minus money out must land on the closing balance to the cent. Says whether it does, and names the rows where it breaks. Free with a PivotBank account.
| Name | Type | Req | Description |
|---|---|---|---|
| pdf_base64 | string | – | For clients without file attachments: the PDF, base64-encoded. |
| statement | object | – | The bank statement PDF the user shared. |
No output schema declared.
No examples provided.
convert_statement Convert a bank statement PDF to Excel, CSV, QuickBooks or Xero ~202
Use this when the user wants a bank statement or credit card statement PDF turned into a spreadsheet: Excel (xlsx), CSV, QuickBooks (QBO), Xero (OFX), Quicken (QIF) or JSON. Reads every transaction (date, description, money in, money out, balance) and checks them against the statement's own running balances, so the reading is proved rather than guessed. Saves the statement to the user's PivotBank account and returns a link to download it in any of those formats. Needs the user to sign in to PivotBank; agents may instead send a Pro API key as 'Authorization: Bearer pvb_live_...'.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | The file name, for your own records. |
| pdf_base64 | string | – | For clients without file attachments: the statement PDF, base64-encoded. 15 MB before encoding at most. |
| statement | object | – | The bank statement PDF the user shared. |
No output schema declared.
No examples provided.
list_supported_banks Banks recognised by name ~89
Lists the banks PivotBank recognises by name, for one country (ISO 3166 alpha-2, e.g. GB, US, ZA) or for all. A statement from a bank not listed still converts: the reader works from the layout, not a per-bank template.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166 alpha-2 code. Leave out for every bank. |
No output schema declared.
No examples provided.
summarise_spending Summarise spending on a bank statement ~89
Use this when the user wants to know where their money went from a bank statement PDF: money in and out, spending by category, top merchants and repeating payments such as subscriptions. Free with a PivotBank account.
| Name | Type | Req | Description |
|---|---|---|---|
| pdf_base64 | string | – | For clients without file attachments: the PDF, base64-encoded. |
| statement | object | – | The bank statement PDF the user shared. |
No output schema declared.
No examples provided.
How do I install the PivotBank MCP server?
PivotBank is a hosted endpoint at https://pivotbank.app/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 · pivotbank.app
claude mcp add --transport http app-pivotbank-pivotbank 'https://pivotbank.app/mcp'
What is the PivotBank MCP server?
PivotBank is an MCP server listed in the public MCP registry as app.pivotbank/pivotbank. Convert bank statement PDFs to Excel, CSV, OFX or QBO, every row checked against the balances. This page covers its hosted endpoint (https://pivotbank.app/mcp).
Is the PivotBank MCP server safe to use?
PivotBank scores 86 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 PivotBank MCP server expose?
PivotBank exposes 4 tools: convert_statement, check_statement_balances, summarise_spending, list_supported_banks. Their descriptions and schemas cost roughly 504 tokens of context every time the server is loaded.
Does the PivotBank MCP server require authentication?
No. We connected to PivotBank without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PivotBank MCP server still maintained?
PivotBank 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.