Remote MCP · Endpoint

PivotBank MCP server

No. PivotBank answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pivotbank.app/mcp

The last check completed an MCP handshake.

Registry name
app.pivotbank/pivotbank
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
550 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Convert bank statement PDFs to Excel, CSV, OFX or QBO, every row checked against the balances.
Listing
From the official MCP registry (active).
Recent checks of PivotBank
CheckedResultHandshake
1 hour agoHandshake completed550 ms
2 days agoHandshake completed535 ms
5 days agoHandshake completed619 ms
7 days agoHandshake completed552 ms
9 days agoHandshake completed542 ms
11 days agoHandshake completed557 ms
13 days agoHandshake completed550 ms
15 days agoHandshake completed924 ms
17 days agoHandshake completed522 ms
19 days agoHandshake completed530 ms
20 days agoHandshake completed539 ms
21 days agoHandshake completed663 ms
22 days agoHandshake completed591 ms
25 days agoHandshake completed583 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with PivotBank and makes no claim about it beyond what these checks measured.