Statement to Budget
REMOTE · WWW.STATEMENTTOBUDGET.COM · SCANNED SEP 26
Turn bank statement PDFs, CSVs, XLSX and OFX into categorised transactions plus a summary.
Available components
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
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 410 tokens (~136/item across 3 items; 3 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the Statement to Budget MCP server?
Statement to Budget is a hosted endpoint at https://www.statementtobudget.com/api/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 · www.statementtobudget.com
claude mcp add --transport http com-statementtobudget-www-bank-statement-convert 'https://www.statementtobudget.com/api/mcp'
{
"mcpServers": {
"com-statementtobudget-www-bank-statement-convert": {
"url": "https://www.statementtobudget.com/api/mcp"
}
}
} {
"servers": {
"com-statementtobudget-www-bank-statement-convert": {
"type": "http",
"url": "https://www.statementtobudget.com/api/mcp"
}
}
} [mcp_servers.com-statementtobudget-www-bank-statement-convert] url = "https://www.statementtobudget.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-statementtobudget-www-bank-statement-convert": {
"type": "remote",
"url": "https://www.statementtobudget.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-statementtobudget-www-bank-statement-convert --url 'https://www.statementtobudget.com/api/mcp' --transport streamable-http
mcp_servers:
com-statementtobudget-www-bank-statement-convert:
url: "https://www.statementtobudget.com/api/mcp" {
"McpServers": {
"com-statementtobudget-www-bank-statement-convert": {
"Transport": "http",
"Url": "https://www.statementtobudget.com/api/mcp"
}
}
} assistant mcp add com-statementtobudget-www-bank-statement-convert -t streamable-http -u 'https://www.statementtobudget.com/api/mcp'
{
"mcpServers": {
"com-statementtobudget-www-bank-statement-convert": {
"type": "http",
"url": "https://www.statementtobudget.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 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.
- 21 Sept 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.
- 19 Sept 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.
- 17 Sept 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.
- 15 Sept 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.
- 13 Sept 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.
- 12 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
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 26 Sept 2026 · Probed https://www.statementtobudget.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.statementtobudget.com | CN=YR2,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | RSA 2048 | SHA256-RSA | 617c970828948169e16164f28b1aaa58e36 |
| SANs: www.statementtobudget.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.statementtobudget.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| statementtobudget.com. | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.statementtobudget.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.statementtobudget.com/api/mcp | HTTPS enforced | 308 | https://www.statementtobudget.com/api/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 →
convert_statement ~150
Upload a bank statement (PDF, CSV, XLS, XLSX, or OFX) as base64 and run AI extraction + categorisation. Returns a session_id plus access.level: "full" when an API key with credit was supplied, otherwise "preview" (5 sample rows, other rows masked) with an unlock_url a human can open to buy the full file for $4.99. Large statements can take 1-3 minutes; if status is "processing", poll get_job.
| Name | Type | Req | Description |
|---|---|---|---|
| content_base64 | string | yes | File bytes encoded as base64 |
| filename | string | yes | Original file name including extension |
| password | string | – | PDF password if the file is locked |
No output schema declared.
No examples provided.
get_job ~33
Poll a conversion job by session_id. Status is processing, complete, or error.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
get_transactions ~55
Fetch categorised transactions and a spending summary for a completed session. Preview sessions return 5 sample rows, locked_rows (date, category, masked description) for the rest, and unlock_url.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
What is the Statement to Budget MCP server?
Statement to Budget is an MCP server listed in the public MCP registry as com.statementtobudget.www/bank-statement-converter. Turn bank statement PDFs, CSVs, XLSX and OFX into categorised transactions plus a summary. This page covers its hosted endpoint (https://www.statementtobudget.com/api/mcp).
Is the Statement to Budget MCP server safe to use?
Statement to Budget 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 Statement to Budget MCP server expose?
Statement to Budget exposes 3 tools: convert_statement, get_job, get_transactions. Their descriptions and schemas cost roughly 238 tokens of context every time the server is loaded.
Does the Statement to Budget MCP server require authentication?
No. We connected to Statement to Budget without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Statement to Budget MCP server still maintained?
Statement to Budget is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.