Bankstatemently MCP server
io.github.bankstatemently/bankstatemently-mcpbankstatementlystreamable-httpv2.1.0Scanned
Convert PDF bank statements into structured transactions, accounts, and balances.
22 tools: 3 can delete or cancel things, 6 do something that can't be undone, 4 change things and 9 only read.
- Reads private data · 1
- Reads text others write · 4
- Can send data out · 1
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here can delete or cancel things and 6 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Bankstatemently MCP server can do
The Bankstatemently MCP server is published by the GitHub account bankstatemently. It has 22 tools. It can delete or cancel things (3 tools: dismiss_statement, update_memory and rate_statement), do things that cannot be undone, such as sending, paying or publishing (adjudicate_transfers, adjudicate_outflows, create_memory, aggregate and 2 more) and create or change data (4 tools: request_upload, convert_statement, categorize_statement and evaluate_benchmark). 9 tools only read.
1 tool reads private data (get_statement); 4 tools bring in text other people can write (convert_statement, list_statements, rate_statement and 1 more); 1 tool can send data out of your system (adjudicate_outflows). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 2.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
22 tools
Deletes or cancels 3Claude Code: deny
dismiss_statementHide a failed, rejected, or cancelled document from future list_statements results.No findings
Why it is in this group
- The name "dismiss_statement" says "dismiss": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Hide a failed, rejected, or cancelled document from future list_statements results. Use this only when the user asks to clear a terminal failed/rejected/cancelled conversion from their history. This is not a delete: it marks the document dismissed and leaves stored data/artifacts untouched.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: false
rate_statementReport how well a previously converted bank statement was parsed: submit a 1-5 rating, optionally with structured feedback at any rating.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Report how well a previously converted bank statement was parsed: submit a 1-5 rating, optionally with structured feedback at any rating. Your rating counts toward the average ratings shown on bankstatemently.com. Calling this again for the same document updates your existing rating without clearing feedback already submitted for it. Returns the stored rating state in the response — there is no separate tool to read your own rating back. Every response includes a "summary" field: use it as the single source of truth for what happened.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: true
update_memoryRename or rescope an existing named memory, or update its situation.No findings
Why it is in this group
- The name "update_memory" says "update": a word for a change.
- The input addresses people (input.scope.dateRange.to): what it sends cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Rename or rescope an existing named memory, or update its situation. The default memory is immutable. Free to use — no credits consumed.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: false
Can't be undone 6Claude Code: ask
adjudicate_outflowsDecide where an "unresolved" debit from list_outflows went (the documents' claims conflict and nothing settles them).Can send data outNo findings
Why it is in this group
- The input addresses people (input.dateRange.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.dateRange.to): what the tool writes goes there.
Description, as the server wrote it Decide where an "unresolved" debit from list_outflows went (the documents' claims conflict and nothing settles them). Pass "verdict" and "transactionIds" when the user has told you; leave "verdict" out to let the AI judge decide the named rows, or every unresolved row. Returns the updated list_outflows answer.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
adjudicate_transfersDecide whether ambiguous pairs from list_transfers are transfers.No findings
Why it is in this group
- The name "adjudicate_transfers" says "transfer": a word for a change that another call does not undo.
- The input addresses people (input.scope.dateRange.to): what it sends cannot be taken back.
Description, as the server wrote it Decide whether ambiguous pairs from list_transfers are transfers. Pass "verdict" when the user has told you; leave it out to let the AI judge decide. Returns the updated list_transfers answer.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
aggregateCompute a single metric (sum/average/count/max/min) over a filtered set of transactions across your converted statements.1 finding
Why it is in this group
- The input addresses people (input.scope.dateRange.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "aggregate" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input addresses people (input.scope.dateRange.to): what it sends cannot be taken back.
Description, as the server wrote it Compute a single metric (sum/average/count/max/min) over a filtered set of transactions across your converted statements. Results are per-currency — never sum across currencies yourself. Scope defaults to all your completed statements; pass "scope" to narrow to specific accounts/products and/or a date range. For "how many credits do I have" / processing quota / remaining pages, use get_credits instead — that is not a transaction.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
create_memoryCreate a named memory: a scoped lens over your accounts and dates with a user-authored name, optional situation ("bookkeeping", "divorce" or "estate"), and ChatScope.No findings
Why it is in this group
- The name "create_memory" says "create": a word for a change.
- The input addresses people (input.scope.dateRange.to): what it sends cannot be taken back.
Description, as the server wrote it Create a named memory: a scoped lens over your accounts and dates with a user-authored name, optional situation ("bookkeeping", "divorce" or "estate"), and ChatScope. Free to use — no credits consumed.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
group_byGroup transactions by a dimension (month/category/counterparty/account/currency) and apply a metric to each group.1 finding
Why it is in this group
- The input addresses people (input.scope.dateRange.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "group_by" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input addresses people (input.scope.dateRange.to): what it sends cannot be taken back.
Description, as the server wrote it Group transactions by a dimension (month/category/counterparty/account/currency) and apply a metric to each group. Results are per-currency. The "counterparty" dimension keys on the printed counterparty, else a printed account mask (••1234), else the description's name tokens, so a rail word or reference number never splits one payee; a line with no key groups under "unknown". Scope defaults to all your completed statements; pass "scope" to narrow to specific accounts/products and/or a date range.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
time_seriesCompute a time series by grouping transactions into week or month buckets and applying a metric — useful for trends.1 finding
Why it is in this group
- The input addresses people (input.scope.dateRange.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "time_series" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input addresses people (input.scope.dateRange.to): what it sends cannot be taken back.
Description, as the server wrote it Compute a time series by grouping transactions into week or month buckets and applying a metric — useful for trends. Scope defaults to all your completed statements; pass "scope" to narrow to specific accounts/products and/or a date range.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Changes things 4Claude Code: ask
categorize_statementRun AI transaction categorization on a previously processed document, then return its category mappings.No findings
Why it is in this group
- The description's first verb is "run": a word for a change.
Description, as the server wrote it Run AI transaction categorization on a previously processed document, then return its category mappings. Returns cached categories with no charge if this document was already categorized. Consumes credits (pooled per page, same rate as the categorize toggle on the website) the first time — free on every re-fetch after. Every response includes a "summary" field: use it as the single source of truth for what happened.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
convert_statementConvert a bank statement PDF into structured data or a spreadsheet.Reads text others writeNo findings
Why it is in this group
- The name "convert_statement" says "convert": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Convert a bank statement PDF into structured data or a spreadsheet. When the user attaches a PDF in the conversation, it arrives automatically as pdf_file — never encode it yourself. Otherwise, pass pdf_url for a public HTTPS link. If your host has no way to reference the attached file at all (no pdf_file/pdf_url equivalent), call request_upload first and pass its upload_id here instead. The base64 pdf parameter is a last resort only, for a caller with no other way to reference the file. To convert several statements in one call, pass upload_ids (the array from a single request_upload call made with count set) instead of pdf/pdf_url/pdf_file/upload_id — mutually exclusive with those four. This batch form only ADMITS each file (queues it, or reports an already-completed duplicate) and returns immediately with a compact per-file status list plus a summary — it never waits for conversion, so call get_statement per document_id once ready rather than expecting inline results here. Returns accounts, transactions, and metadata. output_format "json" (default) returns the data inline, renderable in chat. The other formats (csv, xlsx, qbo, xero) return a time-limited download link instead: present it as a normal link. Every response includes a "summary" field: use it as the single source of truth for what happened. If the conversation is not in English, translate it faithfully into the conversation language; never add details it doesn't contain. Never echo raw status values (e.g. "completed") or field names. Consumes credits (1 per page). Page limit depends on your plan.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
evaluate_benchmarkScore parsed bank statement transactions against the Bankstatemently benchmark ground truth.1 finding
Why it is in this group
- The name "evaluate_benchmark" says "evaluate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "evaluate_benchmark" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "evaluate_benchmark" says "evaluate": a word for a change.
Description, as the server wrote it Score parsed bank statement transactions against the Bankstatemently benchmark ground truth. Accepts a statement_id (e.g. "bsb-001") or content_hash, plus your parsed transactions. Returns extraction accuracy, integrity score, and an overall score. Only statements marked published: true in the catalog can be evaluated — held-out statements return an error. transactions[].originalData is optional but strongly recommended: fetch it via get_statement with data_mode: "original" and pass it through verbatim — an absent originalData scores that transaction's raw-fidelity (parsed) dimension 0; never fabricate a value. Free to use — no credits consumed. Read the benchmark://catalog resource first to see available statements and their published status.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
request_uploadMint a single-use upload URL for pushing a conversation-attached PDF to Bankstatemently before converting it.No findings
Why it is in this group
- The name "request_upload" says "request": a word for a change.
Description, as the server wrote it Mint a single-use upload URL for pushing a conversation-attached PDF to Bankstatemently before converting it. Use this ONLY when you have no other way to reference the attached file (no pdf_file/pdf_url equivalent for this host) — e.g. a code-execution sandbox that can see the file on disk but has no URL for it. Playbook: (1) check your sandbox's uploads/attachments directory first — if the file isn't there yet, the mount can lag behind the conversation; ask the user to re-attach or wait a moment and check again before calling this tool. (2) Call request_upload to get upload_url and upload_id. (3) PUT the raw PDF bytes to upload_url with header Content-Type: application/pdf, e.g.: `curl -X PUT "<upload_url>" -H "Content-Type: application/pdf" --data-binary @<path-to-file>`. (4) Once the PUT succeeds, call convert_statement with upload_id set to the same value — never pdf/pdf_url/pdf_file for this flow. The URL and token are single-use and expire quickly; call request_upload again for a fresh one if the PUT fails partway through — never retry a failed PUT against the same URL. If the PUT fails with a network error or a "host not allowed"-style denial, the sandbox is likely blocking outbound requests to api.bankstatemently.com — tell the user to add api.bankstatemently.com to their host's code-execution allowed-domains setting (on claude.ai: Settings → Capabilities → Code execution) and retry. To convert several statements at once, pass count (1-100) instead of calling this tool once per file: the response returns "uploads", an array of that many { upload_id, upload_url } pairs — PUT each file to its own upload_url, then make ONE convert_statement call with upload_ids set to every upload_id. Free to use — no credits consumed (conversion itself still costs credits, same as any other convert_statement call).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
Only reads 9Show 9 read-only tools
compareSide-by-side metric comparison for two filtered groups of transactions (e.g.No findings
Why it is in this group
- The name "compare" says "compare": a word for reading.
Description, as the server wrote it Side-by-side metric comparison for two filtered groups of transactions (e.g. one category vs another, one month vs another). Scope defaults to all your completed statements; pass "scope" to narrow to specific accounts/products and/or a date range.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_creditsYour remaining Bankstatemently credits — the processing quota, NOT credit/debit transactions.No findings
Why it is in this group
- The name "get_credits" says "get": a word for reading.
Description, as the server wrote it Your remaining Bankstatemently credits — the processing quota, NOT credit/debit transactions. Use for: how many credits do I have, remaining pages, plan limits, quota, how many pages can I upload. 1 credit = 1 page of bank statement processing. Also reports your plan's operational limits (max pages per upload, max upload size, daily spend cap) so you can size a multi-file batch correctly before starting it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_statementFetch the full converted data for a previously processed document.Reads private dataNo findings
Why it is in this group
- The name "get_statement" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "document": it reads documents.
Description, as the server wrote it Fetch the full converted data for a previously processed document. Use this after convert_statement returns a "processing" status, or to re-fetch results. output_format "json" (default) returns the data inline, renderable in chat. The other formats (csv, xlsx, qbo, xero) return a time-limited download link instead: present it as a normal link. data_mode selects which projection of the data you get: omit it for each output_format's existing default behavior. "normalized" is the cleaned, interpreted view; "original" includes each transaction's raw column values exactly as printed on the source PDF (originalData); "enhanced" is a reformatted view of the original columns (csv/xlsx only for now). Fetch data_mode: "original" when you plan to submit results to evaluate_benchmark — pass its originalData through verbatim; an absent originalData scores that benchmark's raw-fidelity dimension 0 for this document. Every response includes a "summary" field: use it as the single source of truth for what happened. If the conversation is not in English, translate it faithfully into the conversation language; never add details it doesn't contain. Never echo raw status values (e.g. "completed") or field names.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_memoriesList your memories, default memory first.No findings
Why it is in this group
- The name "list_memories" says "list": a word for reading.
Description, as the server wrote it List your memories, default memory first. The default memory covers the whole workspace. Named memories include name, situation and scope. Free to use — no credits consumed.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_outflowsEvery debit that left your accounts — in no confirmed transfer between your own accounts, and not a fee — each in ONE destination whose kind is also its next step: "own-account" (a…Reads text others writeNo findings
Why it is in this group
- The name "list_outflows" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it Every debit that left your accounts — in no confirmed transfer between your own accounts, and not a fee — each in ONE destination whose kind is also its next step: "own-account" (a printed account mask that names one of your accounts and no matched credit was found: ask for that account's statement), "account" (a printed account mask for an account outside your statements: request that account's statements; an in-kind move such as securities, crypto or escrow starts as a wire to that account and becomes visible only once the receiving statement is uploaded), "cash" (cash out: where it went cannot be followed, so the cumulative amount is the finding), "name" (a named party: review whether it was household spending) and "unknown" (nowhere the line says; kept visible, one entry per line, never merged). A destination carries the cumulative amount sent, per currency, never a balance. "mayBeOwnAccount" lists debits in an open candidate pair ("may be a move between your own accounts") apart, in no total. "unresolved" lists debits whose documents conflict about where they went (a transfer term and a payment term, no category to settle it) apart, in no total: the documents do not say where they went, so say so and ask the person to confirm. THE way to answer "did money disappear from my accounts, and where do I look next" — never answer it by summing list_transactions rows. Pass "dateRange" ({ from, to }, inclusive, YYYY-MM-DD) to report only debits in that range, for example from a separation date: transfers are matched over the whole scope first, so a transfer whose credit lies outside the range is still a transfer, never an outflow. Scope defaults to all your completed statements; pass "scope" to narrow to specific accounts/products and/or a date range (a scope date range also narrows what is matched — prefer "dateRange").
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_statementsBrowse your previously converted bank statements with pagination and optional status filter.Reads text others writeNo findings
Why it is in this group
- The name "list_statements" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it Browse your previously converted bank statements with pagination and optional status filter.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_transactionsA transaction is a single line as printed on one account's statement — one side of any movement.No findings
Why it is in this group
- The name "list_transactions" says "list": a word for reading.
Description, as the server wrote it A transaction is a single line as printed on one account's statement — one side of any movement. Return a filtered list of transactions across your converted statements, capped at 50 rows. Scope defaults to all your completed statements; pass "scope" to narrow to specific accounts/products and/or a date range. Every response names the scope it actually evaluated (document count + covered date range) and each returned row carries its source document's content_hash so you can cite it. For "how many credits do I have" / processing quota / remaining pages, use get_credits instead — that is not a transaction.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_transfersMatch transfers between your own accounts.No findings
Why it is in this group
- The name "list_transfers" says "list": a word for reading.
Description, as the server wrote it Match transfers between your own accounts. A transfer is TWO transactions — a debit leaving one of your accounts and a credit arriving in another — matched as two sides of the same movement (amount and date aligned); account-level successions (an account closing into a successor) are matched too. A payment to an outside party is not a transfer here: only movements with both sides visible in your statements are matched. THE way to answer any "was money moved between my accounts" / "did I transfer X" question — never try to answer a money-moved-between-accounts question with list_transactions + arithmetic; always call this tool instead. Ties come back as "ambiguous" until decided; call adjudicate_transfers to decide them. Scope defaults to all your completed statements; pass "scope" to narrow to specific accounts/products and/or a date range. Every response reports the match window (in days) it used, even when no transfers are found — a lack of matches is never silent about how hard it looked. To find large movements with NO matching counterpart in your other accounts — e.g. "trace transfers over $10,000; which ones leave without a known destination?" — pass "amountMin": reconciled pairs and successions are filtered to that floor, and the response gains an "unmatched" bucket of large movements (debits leaving, or unexplained credits arriving) with no matching pair, candidate, or succession. Omit amountMin for the ordinary reconciled-pairs answer.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
top_nReturn the top N groups ranked by metric (descending), per-currency for monetary metrics.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Return the top N groups ranked by metric (descending), per-currency for monetary metrics. Scope defaults to all your completed statements; pass "scope" to narrow to specific accounts/products and/or a date range.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__bankstatemently__adjudicate_outflows"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:02 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 13
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.bankstatemently.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://clerk.bankstatemently.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 13 tools that change things (3 destructive, 6 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.bankstatemently.com/mcp: tools/list returned 22 tools to an anonymous client, including dismiss_statement (destructive), update_memory (destructive), rate_statement (destructive), adjudicate_transfers (irreversible), adjudicate_outflows (irreversible) and 8 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "evaluate_benchmark" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "evaluate_benchmark" says "evaluate": a word for a change.
- Warnaggregate
The server marks "aggregate" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input addresses people (input.scope.dateRange.to): what it sends cannot be taken back.
- Warngroup_by
The server marks "group_by" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input addresses people (input.scope.dateRange.to): what it sends cannot be taken back.
- Warntime_series
The server marks "time_series" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input addresses people (input.scope.dateRange.to): what it sends cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 2.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http bankstatemently https://api.bankstatemently.com/mcp --header 'X-API-Key: <your-x-api-key>'claude mcp add --transport http bankstatemently https://api.bankstatemently.com/mcp --header 'X-API-Key: <your-x-api-key>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__bankstatemently__get_statement",
"mcp__bankstatemently__list_statements",
"mcp__bankstatemently__get_credits",
"mcp__bankstatemently__list_memories",
"mcp__bankstatemently__list_transactions",
"mcp__bankstatemently__top_n",
"mcp__bankstatemently__compare",
"mcp__bankstatemently__list_transfers",
"mcp__bankstatemently__list_outflows"
],
"ask": [
"mcp__bankstatemently__request_upload",
"mcp__bankstatemently__convert_statement",
"mcp__bankstatemently__categorize_statement",
"mcp__bankstatemently__adjudicate_transfers",
"mcp__bankstatemently__adjudicate_outflows",
"mcp__bankstatemently__create_memory",
"mcp__bankstatemently__evaluate_benchmark",
"mcp__bankstatemently__aggregate",
"mcp__bankstatemently__group_by",
"mcp__bankstatemently__time_series"
],
"deny": [
"mcp__bankstatemently__dismiss_statement",
"mcp__bankstatemently__update_memory",
"mcp__bankstatemently__rate_statement"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bankstatemently. Review it before you use it.
Capability tags behind 6 rules
- mcp__bankstatemently__convert_statement untrusted-input
- mcp__bankstatemently__get_statement private-data
- mcp__bankstatemently__list_statements untrusted-input
- mcp__bankstatemently__adjudicate_outflows outbound
- mcp__bankstatemently__rate_statement untrusted-input
- mcp__bankstatemently__list_outflows untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.bankstatemently/bankstatemently-mcp/verify?hash=05a48f9e1eb4eb770f93eaabbc1fa41d25eb1ac5546d8d2f2db0041f8d942363" | jq -e '.changed == false'Pinned hash 05a48f9e1eb4, from Nov 16, 2026, 11:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.bankstatemently/bankstatemently-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.bankstatemently/bankstatemently-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:23 UTC.
Bankstatemently MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Bankstatemently MCP server safe?
- No scan can promise that. What its definitions show: 22 tools, 13 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Bankstatemently MCP server delete data?
- Yes. 3 tools can delete, cancel or revoke something: dismiss_statement, update_memory and rate_statement.
Can the Bankstatemently MCP server do things that cannot be undone?
- Yes. 6 tools can send, pay, publish or merge: adjudicate_transfers, adjudicate_outflows, create_memory, aggregate, group_by and time_series.
What tools does the Bankstatemently MCP server have?
- 22 tools: 3 destructive, 6 irreversible, 4 write, 9 read. dismiss_statement, update_memory, rate_statement, adjudicate_transfers, adjudicate_outflows, create_memory, aggregate, group_by and 14 more.
Does the Bankstatemently MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Bankstatemently MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): adjudicate_outflows.
Has the Bankstatemently MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.