Taggun MCP by usefulapi
REMOTE · TAGGUN.USEFULAPI.IO
Scan receipts with Taggun OCR from a URL or file and read receipt-validation campaigns.
Available components
Last scanned (14 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Documents and Files
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 59
First indexed and scored.
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 18 Oct 2026 · Probed https://taggun.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of taggun.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://taggun.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://taggun.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://taggun.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://taggun.usefulapi.io/mcp |
| Authorisation server | https://taggun.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://taggun.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/taggun/ |
| http (plaintext) | http://taggun.usefulapi.io/mcp | Inconclusive | 302 | http://taggun.usefulapi.io/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 →
taggun_export_reference_data Export account reference data (CSV) ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Which list to export. |
No output schema declared.
No examples provided.
taggun_get_campaign Get a validation campaign's rules ~68
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | A campaign id from taggun_list_campaigns. |
No output schema declared.
No examples provided.
taggun_list_campaigns List validation campaigns ~68
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
taggun_scan_receipt_base64 Scan a receipt or invoice from base64 data ~423
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
taggun_scan_receipt_url Scan a receipt or invoice from a URL ~397
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Public https URL of the receipt or invoice file. |
No output schema declared.
No examples provided.
taggun_validate_receipt_campaign_url Validate a receipt against a stored campaign ~298
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.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | 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 | yes | Public https URL of the receipt or invoice file. |
No output schema declared.
No examples provided.
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.
remote · taggun.usefulapi.io
claude mcp add --transport http io-usefulapi-taggun 'https://taggun.usefulapi.io/mcp'
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.