Remote MCP · Endpoint

Bank Statement to CSV (Tanod) MCP server

No. Bank Statement to CSV (Tanod) answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://tanod.dev/mcp/bank-statement

The last check completed an MCP handshake.

Registry name
dev.tanod/bank-statement
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
331 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Bank statement PDFs become CSV, JSON or QBO transactions with dates, amounts and balances.
Listing
From the official MCP registry (active).
Recent checks of Bank Statement to CSV (Tanod)
CheckedResultHandshake
13 minutes agoHandshake completed331 ms
10 days agoHandshake completed350 ms
10 days agoHandshake completed818 ms
11 days agoHandshake completed343 ms
13 days agoHandshake completed319 ms
14 days agoHandshake completed307 ms
14 days agoHandshake completed327 ms
15 days agoHandshake completed972 ms
17 days agoHandshake completed335 ms
19 days agoHandshake completed335 ms
21 days agoHandshake completed331 ms
24 days agoHandshake completed322 ms
26 days agoHandshake completed297 ms
28 days agoHandshake completed342 ms

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

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 Bank Statement to CSV (Tanod) and makes no claim about it beyond what these checks measured.