Statement Normalizer vs Fetch
Side-by-side comparison of two Model Context Protocol servers. Pick the right one for Claude Desktop, Claude Code, or Cursor.
Deterministic bank-statement parsing for AI agents: messy CSV/OFX exports to clean, categorized ledger rows. In-memory only, no storage, no external calls, no L
Comparison
| Feature | Statement Normalizer | Fetch |
|---|---|---|
| Pricing | Free | Free |
| Installs | — | 1 |
| Rating | — | — |
| Verified | — | |
| Hosted | — | — |
| Tools | — | — |
| Category | ai | ai |
| Author | jfortier93 | Community |
| Repo | jfortier93/statement-normalizer-mcp | modelcontextprotocol/servers |
When to pick Statement Normalizer
Deterministic bank-statement parsing for AI agents: messy CSV/OFX exports to clean, categorized ledger rows. In-memory only, no storage, no external calls, no LLM in the loop.
When to pick Fetch
Web content fetching and conversion for efficient LLM usage.
Looking for something else? Browse all MCPs or check trending this week.