Gift Up! MCP by usefulapi
REMOTE · GIFT-UP.USEFULAPI.IO
Read Gift Up! gift cards, orders, items, promotions and transactions (read-only, codes masked).
Available components
Last scanned (8 minutes ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category E-commerce
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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1867 tokens (~143/item across 13 items; 13 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 Management17
- Stability observed for 5 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 60
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 17 Oct 2026 · Probed https://gift-up.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 gift-up.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://gift-up.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://gift-up.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://gift-up.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://gift-up.usefulapi.io/mcp |
| Authorisation server | https://gift-up.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gift-up.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/gift-up/ |
| http (plaintext) | http://gift-up.usefulapi.io/mcp | Inconclusive | 302 | http://gift-up.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 →
giftup_get_company Get company ~41
The Gift Up account this API key belongs to: id, name, currency, whether onboarding is complete and whether the checkout is live. GET /company.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
giftup_get_gift_card Get gift card ~138
One gift card by its code: balance (remainingValue / remainingUnits), status flags, expiry, recipient, order, fulfilment and the full ledger of events (created, redeemed, topped up, voided). Returns the code in full because you asked for this card by code; do not repeat it elsewhere. Read-only: it never redeems or changes the card. GET /gift-cards/{code}.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The gift card code. |
| test_mode | boolean | – | Read the account's test data instead of live data (sends x-giftup-testmode: true). Default false. |
No output schema declared.
No examples provided.
giftup_get_item Get item ~90
One item (gift card product) by id. Pre-generated codes are reduced to a count and masked tails. GET /items/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | The item id (a GUID, from giftup_list_items). |
| test_mode | boolean | – | Read the account's test data instead of live data (sends x-giftup-testmode: true). Default false. |
No output schema declared.
No examples provided.
giftup_get_item_group Get item group ~77
One item group by id. GET /groups/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The item group id (a GUID, from giftup_list_item_groups). |
| test_mode | boolean | – | Read the account's test data instead of live data (sends x-giftup-testmode: true). Default false. |
No output schema declared.
No examples provided.
giftup_get_order Get order ~92
One order by id: totals, purchaser, promotions, custom fields, sales taxes, notes, metadata and payment provider. GET /orders/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order id (a GUID, from giftup_list_orders). |
| test_mode | boolean | – | Read the account's test data instead of live data (sends x-giftup-testmode: true). Default false. |
No output schema declared.
No examples provided.
giftup_get_transaction Get report transaction ~93
One report transaction by id. The gift card code inside is MASKED (at least 6 characters stay hidden). GET /reports/transactions/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| test_mode | boolean | – | Read the account's test data instead of live data (sends x-giftup-testmode: true). Default false. |
| transaction_id | string | yes | The transaction id (a GUID, from giftup_list_transactions). |
No output schema declared.
No examples provided.
giftup_list_gift_cards List gift cards ~321
List gift cards with balance, status flags (canBeRedeemed, hasExpired, notYetValid, isVoided), title, recipient, expiry and the order they came from. Codes are MASKED (at least 6 characters stay hidden); to see one card in full (code and ledger) use giftup_get_gift_card with its code. Filter by state, creation/update time, order, SKU, recipient/purchaser email or payment transaction id. GET /gift-cards.
| Name | Type | Req | Description |
|---|---|---|---|
| created_on_or_after | string | – | Only gift cards created on or after this time (UTC). |
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Results to skip (default 0). Pass the previous reply's next_offset. |
| order_id | string | – | Only gift cards of this order id. |
| payment_transaction_id | string | – | Only gift cards whose payment-provider transaction id matches. |
| purchaser_email | string | – | Only gift cards bought by this purchaser email address. |
| recipient_email | string | – | Only gift cards sent to this recipient email address. |
| sku | string | – | Only gift cards with this private SKU. |
| status | string | – | Only gift cards in this state. |
| test_mode | boolean | – | Read the account's test data instead of live data (sends x-giftup-testmode: true). Default false. |
| updated_on_or_after | string | – | Only gift cards updated on or after this time (UTC). |
No output schema declared.
No examples provided.
giftup_list_item_groups List item groups ~72
List item groups (the sections that organize items in the checkout): id, name, description, sort order, auto-expand. GET /groups.
| Name | Type | Req | Description |
|---|---|---|---|
| test_mode | boolean | – | Read the account's test data instead of live data (sends x-giftup-testmode: true). Default false. |
No output schema declared.
No examples provided.
giftup_list_items List items ~114
List the gift card products on sale (items): name, price, value, price type, availability window, group, stock level, per-order limit, SKU and terms. Pre-generated codes are reduced to a count and masked tails. Optionally only one group. GET /items.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | – | Only items in this item group id. |
| test_mode | boolean | – | Read the account's test data instead of live data (sends x-giftup-testmode: true). Default false. |
No output schema declared.
No examples provided.
giftup_list_locations List locations ~64
List the locations (stores) of the account; their ids filter and label report transactions. GET /locations.
| Name | Type | Req | Description |
|---|---|---|---|
| test_mode | boolean | – | Read the account's test data instead of live data (sends x-giftup-testmode: true). Default false. |
No output schema declared.
No examples provided.
giftup_list_orders List orders ~182
List orders (the purchases that created gift cards), newest first: order number, purchaser, revenue, tip, fees, discount, applied promotions, source, notes, metadata and payment provider. Filter by creation time, purchaser email or source. GET /orders.
| Name | Type | Req | Description |
|---|---|---|---|
| created_on_or_after | string | – | Only orders created on or after this time (UTC). |
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Results to skip (default 0). Pass the previous reply's next_offset. |
| purchaser_email | string | – | Only orders by this purchaser email address. |
| source | string | – | Only orders from this source. |
| test_mode | boolean | – | Read the account's test data instead of live data (sends x-giftup-testmode: true). Default false. |
No output schema declared.
No examples provided.
giftup_list_promotions List promotions ~98
List promotions (checkout discounts and bonus credit): name, published/stopped dates, benefits (percentage and fixed discounts, extra credit), usage counts and revenue, limitations and triggers (items, groups, spend and quantity thresholds, promo code). Read-only. GET /promotions.
| Name | Type | Req | Description |
|---|---|---|---|
| test_mode | boolean | – | Read the account's test data instead of live data (sends x-giftup-testmode: true). Default false. |
No output schema declared.
No examples provided.
giftup_list_transactions List report transactions ~281
The immutable financial transaction log: OrderPlaced (income, fees, tip), GiftCardCreated, CreditAdded, Redeemed, Expired, Unexpired, Voided, Reactivated, with who, where, reason, Gift Up fee and the value change. Gift card codes are MASKED (at least 6 characters stay hidden). Filter by time range, event type, user email, location id or one gift card code. GET /reports/transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Only events of the gift card with this code. |
| event_occurred_on_or_after | string | – | Only events on or after this time (UTC). |
| event_occurred_on_or_before | string | – | Only events on or before this time (UTC). |
| events | array | – | Only these event types. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| locations | array | – | Only events at these location ids (see giftup_list_locations). |
| offset | integer | – | Results to skip (default 0). Pass the previous reply's next_offset. |
| test_mode | boolean | – | Read the account's test data instead of live data (sends x-giftup-testmode: true). Default false. |
| users | array | – | Only events generated by these user email addresses. |
No output schema declared.
No examples provided.
How do I install the Gift Up! MCP by usefulapi server?
Gift Up! MCP by usefulapi is a hosted endpoint at https://gift-up.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 · gift-up.usefulapi.io
claude mcp add --transport http io-usefulapi-gift-up 'https://gift-up.usefulapi.io/mcp'
What is the Gift Up! MCP by usefulapi server?
Gift Up! MCP by usefulapi is listed in the public MCP registry as io.usefulapi/gift-up. Read Gift Up! gift cards, orders, items, promotions and transactions (read-only, codes masked). This page covers its hosted endpoint (https://gift-up.usefulapi.io/mcp).
Is the Gift Up! MCP by usefulapi server safe to use?
Gift Up! 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 Gift Up! MCP by usefulapi server expose?
Gift Up! MCP by usefulapi exposes 13 tools: giftup_get_company, giftup_list_gift_cards, giftup_get_gift_card, giftup_list_orders, giftup_get_order, and 8 more. Their descriptions and schemas cost roughly 1,663 tokens of context every time the server is loaded.
Does the Gift Up! MCP by usefulapi server require authentication?
Yes. Gift Up! 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 Gift Up! MCP by usefulapi server still maintained?
Gift Up! MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.