# Taggun MCP by usefulapi (remote · taggun.usefulapi.io)

Scan receipts with Taggun OCR from a URL or file and read receipt-validation campaigns.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `taggun.usefulapi.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-taggun/taggun.md), [page](https://verifymcp.io/servers/io-usefulapi-taggun/taggun)

## Channel facts

- Endpoint: `https://taggun.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1566 tokens (~261/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Taggun MCP by usefulapi server?

Taggun MCP by usefulapi is a hosted endpoint at https://taggun.usefulapi.io/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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-taggun 'https://taggun.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-taggun": {
      "url": "https://taggun.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-taggun": {
      "type": "http",
      "url": "https://taggun.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-taggun]
url = "https://taggun.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-taggun": {
      "type": "remote",
      "url": "https://taggun.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-taggun --url 'https://taggun.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-taggun:
    url: "https://taggun.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-taggun": {
      "Transport": "http",
      "Url": "https://taggun.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-taggun -t streamable-http -u 'https://taggun.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-taggun": {
      "type": "http",
      "url": "https://taggun.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 62, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 59)

First indexed and scored.

## MCP tools (6)

### `taggun_scan_receipt_url` (~397 tokens)

Scan a receipt or invoice from a URL

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.

Input parameters:

- `detail` (string): simple (default) = totals, tax, date and merchant. verbose = also line items, payment type, per-field metadata and enabled fraud/feature fields.
- `extract_line_items` (boolean): Verbose only: false = skip line-item extraction (default true).
- `extract_time` (boolean): true = return the time of day when found on the receipt (otherwise 12:00:00).
- `ignore_merchant_name` (string): A name to ignore if detected as the merchant, such as a customer name.
- `keep_stored` (boolean): Default false: the document and its extracted data are NOT stored by Taggun (incognito). true = Taggun stores them (up to 3 years), which enables later duplicate/similarity detection but keeps person…
- `language` (string): Optional language hint (en, ar, kh, th, he, ...). Leave out for automatic detection.
- `near` (string): A location (city, state, country) that helps identify the merchant.
- `url` (string, required): Public https URL of the receipt or invoice file.

### `taggun_scan_receipt_base64` (~423 tokens)

Scan a receipt or invoice from base64 data

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.

Input parameters:

- `content_type` (string, required): The file's media type.
- `detail` (string): simple (default) = totals, tax, date and merchant. verbose = also line items, payment type, per-field metadata and enabled fraud/feature fields.
- `extract_line_items` (boolean): Verbose only: false = skip line-item extraction (default true).
- `extract_time` (boolean): true = return the time of day when found on the receipt (otherwise 12:00:00).
- `filename` (string): File name, for example receipt.jpg (default derived from content_type).
- `ignore_merchant_name` (string): A name to ignore if detected as the merchant, such as a customer name.
- `image_base64` (string, required): The file content, base64-encoded (a data: URL prefix is accepted).
- `keep_stored` (boolean): Default false: the document and its extracted data are NOT stored by Taggun (incognito). true = Taggun stores them (up to 3 years), which enables later duplicate/similarity detection but keeps person…
- `language` (string): Optional language hint (en, ar, kh, th, he, ...). Leave out for automatic detection.
- `near` (string): A location (city, state, country) that helps identify the merchant.

### `taggun_validate_receipt_campaign_url` (~298 tokens)

Validate a receipt against a stored campaign

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.

Input parameters:

- `campaign_id` (string, required): A campaign id from taggun_list_campaigns.
- `keep_stored` (boolean): Default false: the document and its extracted data are NOT stored by Taggun (incognito). true = Taggun stores them (up to 3 years), which enables later duplicate/similarity detection but keeps person…
- `language` (string): Optional language hint (en, ar, kh, th, he, ...). Leave out for automatic detection.
- `near` (string): A location (city, state, country) that helps identify the merchant.
- `url` (string, required): Public https URL of the receipt or invoice file.

### `taggun_list_campaigns` (~68 tokens)

List validation campaigns

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.

### `taggun_get_campaign` (~68 tokens)

Get a validation campaign's rules

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}.

Input parameters:

- `campaign_id` (string, required): A campaign id from taggun_list_campaigns.

### `taggun_export_reference_data` (~104 tokens)

Export account reference data (CSV)

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.

Input parameters:

- `kind` (string, required): Which list to export.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-taggun/taggun#diagnostics

## Score history

- 2026-10-18: 64
- 2026-10-17: 64
- 2026-10-16: 63
- 2026-10-15: 63
- 2026-10-14: 62
- 2026-10-13: 60
- 2026-10-12: 59

## Common questions

### What is the Taggun MCP by usefulapi server?

Taggun MCP by usefulapi is listed in the public MCP registry as io.usefulapi/taggun. Scan receipts with Taggun OCR from a URL or file and read receipt-validation campaigns. This page covers its hosted endpoint (https://taggun.usefulapi.io/mcp).

### Is the Taggun MCP by usefulapi server safe to use?

Taggun MCP by usefulapi scores 64 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 Taggun MCP by usefulapi server expose?

Taggun MCP by usefulapi exposes 6 tools: taggun_scan_receipt_url, taggun_scan_receipt_base64, taggun_validate_receipt_campaign_url, taggun_list_campaigns, taggun_get_campaign, taggun_export_reference_data. Their descriptions and schemas cost roughly 1,358 tokens of context every time the server is loaded.

### Does the Taggun MCP by usefulapi server require authentication?

Yes. Taggun MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Taggun MCP by usefulapi server still maintained?

Taggun MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://taggun.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/taggun/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-taggun/taggun.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-taggun/taggun.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-taggun/taggun