Taggun MCP by usefulapi

Each tool targets a distinct operation (export reference data, read campaigns, scan, validate), and the base64 vs URL split is signaled clearly in the names. The only mild overlap is between taggun_scan_receipt_url and taggun_validate_receipt_campaign_url, since both scan a URL, but the validate tool's campaign-checking purpose is clearly spelled out.

All tools use a uniform snake_case verb_noun pattern with a consistent taggun_ prefix (export_reference_data, get_campaign, list_campaigns, scan_receipt_base64/url, validate_receipt_campaign_url). The read vs scan split is even reflected in the verbs (get/list/export vs scan/validate).

Six tools is well-scoped for a receipt-scanning and validation API, with each tool earning its place (two scan input modes, one validation path, two campaign reads, one reference-data export). Nothing feels redundant or missing at the count level.

The core lifecycle is covered: scan receipts (base64 and URL) and validate against campaigns, plus campaign and reference-data reads. Minor gaps exist for campaign management (no create/update/delete campaign) and no retrieval of past scan results, but these are outside the primary scanning purpose and workable.