Taggun MCP by usefulapi
io.usefulapi/taggunusefulapi.iostreamable-httpv1.27.4Scanned
Scan receipts with Taggun OCR from a URL or file and read receipt-validation campaigns.
6 tools: 3 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 6
- Can send data out · 2
- 1 finding
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Taggun MCP by usefulapi can do
The Taggun MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 6 tools. It can create or change data (3 tools: taggun_scan_receipt_url, taggun_scan_receipt_base64 and taggun_validate_receipt_campaign_url), but cannot delete data. 3 tools only read.
6 tools bring in text other people can write (taggun_scan_receipt_url, taggun_scan_receipt_base64, taggun_validate_receipt_campaign_url and 3 more); 2 tools can send data out of your system (taggun_scan_receipt_url and taggun_validate_receipt_campaign_url).
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Last scanned Oct 25, 2026, version 1.27.4.
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.
6 tools
Changes things 3Claude Code: ask
taggun_scan_receipt_base64WRITE: this scan counts against YOUR Taggun quota and plan (free for the first 30 days or 1,000 scans, then billed per scan by Taggun), even if the receipt fails validation; it is …Reads text others writeNo findings
Why it is in this group
- The description's first verb is "write": 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 WRITE: this scan counts against YOUR Taggun quota and plan (free for the first 30 days or 1,000 scans, then billed per scan by Taggun), even if the receipt fails validation; it is never retried automatically. Document content is not logged by this server. Extract structured data from a receipt or invoice sent as base64 (JPEG, PNG, GIF, HEIF/HEIC or PDF; the base64 text is capped at 2,000,000 characters, about 1.5 MB of file; for larger files use taggun_scan_receipt_url). POST /api/receipt/v1/{simple|verbose}/encoded.
Annotations the server declares
- title: Scan a receipt or invoice from base64 data
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
taggun_scan_receipt_urlWRITE: this scan counts against YOUR Taggun quota and plan (free for the first 30 days or 1,000 scans, then billed per scan by Taggun), even if the receipt fails validation; it is …Reads text others writeCan send data out1 finding
Why it is in this group
- The description's first verb is "write": 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.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...P addresses, localhost, internal names, credentials or non-default ports. POST /api/receipt..."
Description, as the server wrote it WRITE: this scan counts against YOUR Taggun quota and plan (free for the first 30 days or 1,000 scans, then billed per scan by Taggun), even if the receipt fails validation; it is never retried automatically. Document content is not logged by this server. Extract structured data (merchant, date, total, tax, and in verbose mode line items) from a receipt or invoice at a public https URL (JPEG, PNG, GIF, HEIF/HEIC or PDF up to 5 pages, max 20 MiB). The URL must be a public host name: no IP addresses, localhost, internal names, credentials or non-default ports. POST /api/receipt/v1/{simple|verbose}/url.
Annotations the server declares
- title: Scan a receipt or invoice from a URL
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
taggun_validate_receipt_campaign_urlWRITE: this scan counts against YOUR Taggun quota and plan (free for the first 30 days or 1,000 scans, then billed per scan by Taggun), even if the receipt fails validation; it is …Reads text others writeCan send data outNo findings
Why it is in this group
- The name "taggun_validate_receipt_campaign_url" says "validate": a word for reading.
- The description's first verb is "write": 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.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it WRITE: this scan counts against YOUR Taggun quota and plan (free for the first 30 days or 1,000 scans, then billed per scan by Taggun), even if the receipt fails validation; it is never retried automatically. Document content is not logged by this server. Scan a receipt at a public https URL and check it against the rules of a campaign stored on your Taggun account (dates, merchants, products, balance owing, fraud checks). Returns pass/fail with reasons. Needs the Campaign Validation feature on your Taggun plan; use taggun_list_campaigns for the ids. Same URL rules as taggun_scan_receipt_url. POST /api/validation/v1/campaign/receipt-validation/url.
Annotations the server declares
- title: Validate a receipt against a stored campaign
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 3Show 3 read-only tools
taggun_export_reference_dataRead the reference data stored on your Taggun account as CSV: product_categories (the category taxonomy), known_merchants (merchant names and locations used for matching) or produc…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
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 Read the reference data stored on your Taggun account as CSV: product_categories (the category taxonomy), known_merchants (merchant names and locations used for matching) or product_codes (expected product codes). Read-only; does not use a scan. The text is cut at 40,000 characters. GET /api/account/v1/{product-categories|known-merchants|known-product-codes}/export.
Annotations the server declares
- title: Export account reference data
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
taggun_get_campaignThe stored validation rules of one campaign (dates, merchants, products, fraud checks, SmartValidate prompts).Reads text others writeNo findings
Why it is in this group
- The name "taggun_get_campaign" says "get": a word for reading.
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 The stored validation rules of one campaign (dates, merchants, products, fraud checks, SmartValidate prompts). Does not use a scan. GET /api/validation/v1/campaign/settings/{campaignId}.
Annotations the server declares
- title: Get a validation campaign's rules
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
taggun_list_campaignsList the ids of the receipt-validation campaigns stored on your Taggun account (an empty list is normal).Reads text others writeNo findings
Why it is in this group
- The name "taggun_list_campaigns" says "list": a word for reading.
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 List the ids of the receipt-validation campaigns stored on your Taggun account (an empty list is normal). Does not use a scan. Needs the Campaign Validation feature; without it Taggun answers that the feature must be enabled. GET /api/validation/v1/campaign/settings/list.
Annotations the server declares
- title: List validation campaigns
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
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:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://taggun.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://taggun.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
The description mentions "credentials".
What this check looks forMatched text
description: "...P addresses, localhost, internal names, credentials or non-default ports. POST /api/receipt..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://taggun.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://taggun.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.27.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http taggun https://taggun.usefulapi.io/mcpclaude mcp add --transport http taggun https://taggun.usefulapi.io/mcpRun 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__taggun__taggun_list_campaigns",
"mcp__taggun__taggun_get_campaign",
"mcp__taggun__taggun_export_reference_data"
],
"ask": [
"mcp__taggun__taggun_scan_receipt_url",
"mcp__taggun__taggun_scan_receipt_base64",
"mcp__taggun__taggun_validate_receipt_campaign_url"
],
"deny": []
}
}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 taggun. Review it before you use it.
Capability tags behind 6 rules
- mcp__taggun__taggun_scan_receipt_url untrusted-input, outbound
- mcp__taggun__taggun_scan_receipt_base64 untrusted-input
- mcp__taggun__taggun_validate_receipt_campaign_url untrusted-input, outbound
- mcp__taggun__taggun_list_campaigns untrusted-input
- mcp__taggun__taggun_get_campaign untrusted-input
- mcp__taggun__taggun_export_reference_data 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.usefulapi/taggun/verify?hash=80fa39be66570b73f24c7c98c99ff2b33e9418bebe4272b57de028ef9189dd1e" | jq -e '.changed == false'Pinned hash 80fa39be6657, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/taggun/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/taggun)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
Taggun MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Taggun MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Taggun MCP by usefulapi delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Taggun MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Taggun MCP by usefulapi have?
- 6 tools: 3 write, 3 read. taggun_scan_receipt_url, taggun_scan_receipt_base64, taggun_validate_receipt_campaign_url, taggun_list_campaigns, taggun_get_campaign and taggun_export_reference_data.
Does the Taggun MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Taggun MCP by usefulapi send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): taggun_scan_receipt_url and taggun_validate_receipt_campaign_url.
Has the Taggun MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.